> For the complete documentation index, see [llms.txt](https://creed-v-2-tm.gitbook.io/creed-v.2-tm-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://creed-v-2-tm.gitbook.io/creed-v.2-tm-docs/stay-undetected/introduction.md).
# Introduction
## Why Most Cheaters Get Caught:
### If you were an admin of the game spectating yourself, would you think you were cheating? If the answer is yes, then likely the anti-cheat can easily find out you're using cheats. With modern technology and millions of dollars being put into anti-cheats, they're pretty good at detecting artificial gaming behavior.
{% hint style="info" %}
However, this is not to say that there isn't TONS of people that have gotten skilled at using cheats while **staying completely undetected**. There is a lot of people that have learned to cheat without getting banned, and *you can too.*
{% endhint %}
## So I got lessons for you!
---
# 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://creed-v-2-tm.gitbook.io/creed-v.2-tm-docs/stay-undetected/introduction.md?ask=&goal=
```
`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.