> For the complete documentation index, see [llms.txt](https://featherfrogs.gitbook.io/featherfrogs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://featherfrogs.gitbook.io/featherfrogs/featherland/a-pocket-universe/a-task-force.md).

# 🎯┊A Task Force

![](/files/1c4Obnj7fGT9TKxK2oSt)

## Never done before...

They all agreed that to banish the Galactic Frogs they would need to take back their sovereigns: The Kings and Queens who were still being held captive. With their reinstatement order might be found again in FeatherLand. To do this a task force would need to be assembled consisting of an army of strong FeatherFrogs but few of which now remained. Therefore, in order to breed an army strong enough, and quick enough, many sacrifices would have to be made. They would also have to do what had never been done before and enter the secret chamber of ‘Rejuvenation’


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://featherfrogs.gitbook.io/featherfrogs/featherland/a-pocket-universe/a-task-force.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
