# Mass Fud Outbreak
With the massive FUD circulating on Twitter, Fluffy Fudders are now ready to take it up a notch to **spread the FUD** across all social medias like wildfire.\
\
First of all, our AI agents will summarise and craft a **powerful thread of FUD** revolving our targeted project from information circulating on Twitter. \
\
Fluffies will then be incentivised to like, retweet and comment to **boost Twitter algorithm** to maximise engagement. Link of threads will be **disseminated throughout** known communities (TG/Discord/Reddit/Wechat) and shared across all important channels by our AI Agents.\
\
As different FUD populates around the relevant **"$"** and **"#"** signs on Twitter, panic and chaos bound to arise, leading to **widespread fear** and eventually a significant decline in the project's chart.\
\
To ensure a successful outbreak (more contagious than Covid), Fluffies work **hand in hand** with our Automated AI Agents. More details here: [X (Twitter) Onslaught](/fluffy-fudders/how-do-fluffies-fud/stage-4-automated-ai-agents/x-twitter-onslaught.md).
Everything is fine until it it not...
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://fluffy-fudders.gitbook.io/fluffy-fudders/how-do-fluffies-fud/stage-3-fluffies-the-fud-syndicate/mass-fud-outbreak.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.