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/nobodyohm-web/thot/triagegit clone --depth 1 https://github.com/nobodyohm-web/ThotWrote 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/nobodyohm-web/thot/triage)<a href="https://agentmods.dev/commands/nobodyohm-web/thot/triage"><img src="https://agentmods.dev/badge/commands/nobodyohm-web/thot/triage.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.00019 | $0.00195 |
| Opus 5 | $0.00010 | $0.00097 |
| Sonnet 5 | $0.00004 | $0.00039 |
| Haiku 4.5 | $0.00002 | $0.00019 |
Grade A, and why
triage 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 3d 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
Applique la méthode vulnerability-triage aux findings qui concernent $1.
Pour chacun, dans cet ordre :
auditpour les lister, puiscallerssur le symbole qui contient le sink.- Nomme l'entrée concrète qui atteint ce sink — un argument HTTP, un champ de formulaire, une variable d'environnement, un fichier lu. Si tu ne peux pas la nommer, ce n'est pas un finding : dis-le et passe au suivant.
- Écris le scénario d'échec en une phrase, avec la charge utile exacte.
Termine par une liste courte : ce qui est exploitable, ce qui ne l'est pas, et pourquoi. Ne propose aucune correction avant que j'aie validé le tri.
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.
- 3d ago First seen · 18 lines · 19 tokens per session scan A bfcdb08e3eb7
triage is a command published in the GitHub repository nobodyohm-web/Thot (0 stars, last pushed 9d ago), licensed MIT. It adds 19 tokens to every session and 195 once invoked, about $0.0001 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-31.
Other commands, from other repositories
explain-error
Explain Stripe error codes and provide solutions with code examples.
check
CodeDNA coverage report — find unannotated files and stale usedby references.
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.