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/amadeusitgroup/otter/fix-auditgit clone --depth 1 https://github.com/AmadeusITGroup/otterWrote 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/amadeusitgroup/otter/fix-audit)<a href="https://agentmods.dev/commands/amadeusitgroup/otter/fix-audit"><img src="https://agentmods.dev/badge/commands/amadeusitgroup/otter/fix-audit.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.00000 | $0.00062 |
| Opus 5 | $0.00000 | $0.00031 |
| Sonnet 5 | $0.00000 | $0.00012 |
| Haiku 4.5 | $0.00000 | $0.00006 |
Grade A, and why
fix-audit 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
Fix Audit Vulnerabilities
Fix the critical audit vulnerabilities blocking a PR. Usage: /fix-audit <pr_number>
Follow the instructions in .agents/fix-audit.md, replacing every occurrence of PR_NUMBER with $ARGUMENTS.
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 · 6 lines · 0 tokens per session scan A 2ead69f92633
fix-audit is a command published in the GitHub repository AmadeusITGroup/otter (57 stars, last pushed today), licensed BSD-3-Clause. It costs nothing until one of its globs matches a file; then it loads 62 tokens. 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
fix-tickets
Autonomously fix one or more speckit-companion GitHub issues with the SpecKit Companion pipeline — clean branch, fix, review, PR, merge, reinstall — then write a manual-verification report. Self-hosting build loop.
ship-ticket
Ship an ALREADY-BUILT ticket — code review → PR → merge → learnings → install-local. Skips the build (you built it in SpecKit Companion). The tail of /fix-tickets, no rebuild.
bench-capture
Score the 2 bench variant folders for one size (build/acceptance/regression/conventions/capture + rubric + cross-solution review), record, report, and reset.
ship
Review code, update docs, and package a new version (project).
install-local
Bump version and install both extensions locally (VS Code + spec-kit).
bench-prep
Clean + arm the 2 bench variant folders for one size, ready to run in VS Code.