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.
git clone --depth 1 https://github.com/wgo-audit/codeWrote 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/wgo-audit/code/cost)<a href="https://agentmods.dev/commands/wgo-audit/code/cost"><img src="https://agentmods.dev/badge/commands/wgo-audit/code/cost/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/wgo-audit/code/cost"><img src="https://agentmods.dev/badge/commands/wgo-audit/code/cost.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00021 | $0.00491 |
| Opus 5.5 | $0.00008 | $0.00196 |
| Sonnet 5.5 | $0.00004 | $0.00098 |
| Haiku 4.5 | $0.00002 | $0.00049 |
Grade A, and why
cost 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 1mo 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
/cost
Invoke this as wgo:cost in Codex, /wgo:cost in Claude, or /wgo-cost in
OpenCode.
Load and use the WGO skill. Resolve the newest dated audit root with its
references/common/audit-root.md, then read the audit platform recorded in
audit-brief.md and run exactly one matching workflow:
- Codex:
references/common/cost-estimation.md; - Claude:
references/common/cost-estimation-claude.md; or - OpenCode:
references/common/cost-estimation-opencode.md.
Do not inspect a provider's session store or apply its usage schema to an audit
recorded on another platform. If the platform is missing, ambiguous, or
unsupported, write an Unreconciled cost control naming that limitation rather
than guessing.
This is a read-only analysis of accessible provider-native session records that
writes <audit-root>/controls/cost-estimate.md and the alias-only
<audit-root>/controls/cost-calculation.json. Keep provider-native manifests
and independent pass files under tmp_debug/wgo-cost/<audit-id>/, outside the
audit root. Then update <audit-root>/manifest.json at
execution.costEstimate with the result's exact total or explicitly labeled
unreconciled subtotal.
Do not install a package, invoke ccusage, add a helper program, or use an
OS-specific binary.
The active-platform coordinator discovers the audit descendants from recorded
collaboration and task-lifecycle provenance, freezes the manifest before any
calculation, and runs exactly two independent calculations over that unchanged
manifest using the worker configuration in the selected provider workflow.
If an earlier immutable manifest is unreconciled because of a demonstrated
provider-schema adapter error, preserve it and create the workflow's versioned
repair manifest and matching result files.
Never identify an included session solely by date, CWD, folder, or model; those
may corroborate recorded provenance only.
After every calculation or refresh, follow
references/templates/cost-estimate-template.md to replace the manifest cost
summary and validate manifest.json again.
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.
- 1mo ago First seen · 47 lines · 21 tokens per session scan A ac2ad0208264
cost is a command published in the GitHub repository wgo-audit/code (2 stars, last pushed 2mo ago), licensed MIT. It adds 21 tokens to every session and 491 once invoked, about $0.0001 per session on Opus 5.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
audit
Scan for non-kernel money math. Rebuild critical flows as JournalEntrys. Replay and prove. Complements /ledger-verify.
reconcile
Assumptions → Money.from → cited, balanced JournalEntry → Ledger.apply. Output entries + proof.
valuation-methods
Valuation methods analysis — multiples, DCF inputs, PEG integration, valuation assumption extraction.
cost-per-task
Compute cost-per-successful-task unit economics from usage and cost data, including retries, failures, and quality thresholds.
audit-checklist
Perform an internal audit, review controls, or prepare for an external financial audit.
scan
Scan AWS account for cost optimization.