# Commands

These are the availabe commands

You can use \<prefix> help to see all the commands too, but here are more detailled ;)

{% content-ref url="commands/social-commands" %}
[social-commands](https://trihammerdocs.gitbook.io/trihammer/commands/social-commands)
{% endcontent-ref %}

{% content-ref url="commands/utility-commands" %}
[utility-commands](https://trihammerdocs.gitbook.io/trihammer/commands/utility-commands)
{% endcontent-ref %}

{% content-ref url="commands/music-commands" %}
[music-commands](https://trihammerdocs.gitbook.io/trihammer/commands/music-commands)
{% endcontent-ref %}

{% content-ref url="commands/moderation-commands" %}
[moderation-commands](https://trihammerdocs.gitbook.io/trihammer/commands/moderation-commands)
{% endcontent-ref %}

{% content-ref url="commands/configuration-commands" %}
[configuration-commands](https://trihammerdocs.gitbook.io/trihammer/commands/configuration-commands)
{% endcontent-ref %}

{% hint style="info" %}
In the list of commands, you will see 2 fields, < > and \[ ]. All the things inside of < > are required, and all the things inside of \[ ] are optional
{% endhint %}


---

# 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://trihammerdocs.gitbook.io/trihammer/commands.md?ask=<question>
```

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.