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/wgo-audit/code/statusgit clone --depth 1 https://github.com/wgo-audit/codeWhat 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.00244 |
| Opus 5 | $0.00010 | $0.00122 |
| Sonnet 5 | $0.00004 | $0.00049 |
| Haiku 4.5 | $0.00002 | $0.00024 |
Grade A, and why
status 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 yesterday.
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
/status
Invoke this as wgo:status in Codex, /wgo:status in Claude, or
/wgo-status in OpenCode.
Load and use the WGO skill. Resolve the newest dated audit root with its
references/common/audit-root.md. Read, without modifying:
<audit-root>/audit-checklist.md<audit-root>/controls/open-items.md<audit-root>/evidence/source-access-register.md- relevant completed reviewer reports when their closeout is unclear
Report each selected reviewer's state, factual completion condition, next action,
recommended next reviewer, material source-access limits, and open-item counts by
Type and priority. If the audit files do not exist, direct the auditor to
wgo:onboard. The checklist is the only work/status view; do not reconstruct a
second status table. Treat rerun-pending as pending work with a completed
prior pass, not as never reviewed.
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.
- yesterday First seen · 27 lines · 19 tokens per session scan A 98b8ed0d9280
status is a command published in the GitHub repository wgo-audit/code (2 stars, last pushed 9d ago), licensed MIT. It adds 19 tokens to every session and 244 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
krait
Run a complete multi-phase security audit on the target codebase.
krait-poc
Write and run a valid Foundry proof-of-concept that proves (or disproves) a Solidity exploit by asserting the actual harm on a forked chain or against local source.
init-brief
Initialize a briefloop workspace using conversational onboarding.
layout
Audit pipeline: choose how the manifest is stored — sharded (an index plus one file per phase: fewer tokens per phase run, parallel-safe across worktrees) or single-file (one file, one diff, no index). A layout CHOICE, not a version upgrade: both shapes are current, neither goes out of date, and this command moves in…
usage
Audit pipeline: token spend attributed by phase, task, model, author and time — with cache economics, cost-per-task and a usage trend. Read-only (never mutates the manifest).
krait-review
Re-examine findings killed by the Critic's automatic gates. Catches over-filtering without compromising the main report's zero-FP standard.