Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/gaia-react/gaia/gaia-forensicsgit clone --depth 1 https://github.com/gaia-react/gaiaWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/gaia-react/gaia/gaia-forensics)<a href="https://agentmods.dev/commands/gaia-react/gaia/gaia-forensics"><img src="https://agentmods.dev/badge/commands/gaia-react/gaia/gaia-forensics.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00044 | $0.00133 |
| Opus 5 | $0.00022 | $0.00067 |
| Sonnet 5 | $0.00009 | $0.00027 |
| Haiku 4.5 | $0.00004 | $0.00013 |
Grade A, and why
gaia-forensics scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Run the GAIA forensics workflow with these arguments: $ARGUMENTS
Read .claude/skills/gaia/references/forensics.md from the project root and follow it exactly. That reference is written to consume an argument string, treat the arguments above as that input. If no arguments were provided, follow the reference's no-argument path.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 10 lines · 44 tokens per session scan A 81057cc0ee04
gaia-forensics is a command published in the GitHub repository gaia-react/gaia (23 stars, last pushed today), licensed MIT. It adds 44 tokens to every session and 133 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
pr-description
Generate a pull request description based on the changes in the current branch.
push-changes
If no topic provided, just document the recent changes. If a topic is provided, focus on documenting that topic.
create-PR
Command "create-PR" from bartstc/vite-ts-react-template, covering create a pr against this branch: $arguments, follow these steps and remember.
security-sast
Static Application Security Testing (SAST) for code vulnerability analysis across multiple languages and frameworks.
security-sast
Static Application Security Testing (SAST) for code vulnerability analysis across multiple languages and frameworks.
git
Git operations with intelligent commit messages and workflow optimization.