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/solanabr/auditor-skillWrote 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/solanabr/auditor-skill/economic-sim)<a href="https://agentmods.dev/commands/solanabr/auditor-skill/economic-sim"><img src="https://agentmods.dev/badge/commands/solanabr/auditor-skill/economic-sim/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/solanabr/auditor-skill/economic-sim"><img src="https://agentmods.dev/badge/commands/solanabr/auditor-skill/economic-sim.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.00049 | $0.00273 |
| Opus 5.5 | $0.00020 | $0.00109 |
| Sonnet 5.5 | $0.00010 | $0.00055 |
| Haiku 4.5 | $0.00005 | $0.00027 |
Grade A, and why
auditor:economic-sim 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
auditor-skill — Economic Simulation
Arguments: $ARGUMENTS
- Model the attack: capital / setup cost, extractable value, atomicity (single-tx / multi-slot), flash-loanable ceilings per venue.
- Compute whether profit > cost at any manipulation level (e.g. cost to move spot price 1 / 5 / 10 %).
- If a Surfpool mainnet-fork is available, reproduce the sequence against forked pool state and record the net P/L. The fork fetches that state from its RPC datasource, which receives the program ids and account addresses it reads: record the provider domain (the host's last two DNS labels) for the report's outside-service disclosure (
OUTPUT-RULES.mdRule 11b), never a URL with a key. - Produce the quantified PoC that Rule 5b requires for High / Critical economic findings — dollar figures, not yes/no.
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 Changed 42c86ac4a742
- 1mo ago First seen · 16 lines · 49 tokens per session scan A 00e6bfa440c7
auditor:economic-sim is a command published in the GitHub repository solanabr/auditor-skill (61 stars, last pushed today), licensed MIT. It adds 49 tokens to every session and 273 once invoked, about $0.0002 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-30.
Other commands, from other repositories
competitive
Competitive landscape analysis — peer positioning, market-share dynamics, moat assessment.
unit-economics
../../vertical-plugins/business-intelligence/commands/unit-economics.md.
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.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.