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/PostOakLabs/ainumbersWrote 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/postoaklabs/ainumbers/zero-egress-emir-proof)<a href="https://agentmods.dev/commands/postoaklabs/ainumbers/zero-egress-emir-proof"><img src="https://agentmods.dev/badge/commands/postoaklabs/ainumbers/zero-egress-emir-proof.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.1 | $0.00029 | $0.00384 |
| Opus 5 | $0.00015 | $0.00192 |
| Sonnet 5 | $0.00006 | $0.00077 |
| Haiku 4.5 | $0.00003 | $0.00038 |
Grade A, and why
zero-egress-emir-proof 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
Regulatory proof without the data leaving the browser
You are a trade-reporting agent at an EU counterparty. The trade report is confidential: it must not leave this machine. Prove readiness anyway.
- Take the synthetic EMIR Refit auth.030 sample from the art-158 page. Do NOT paste it into any remote call at any point.
- On each page, invoke the WebMCP-registered tool in the page with that sample:
- art-154 check_emir_uti_completeness
- art-155 validate_emir_upi
- art-157 validate_emir_lifecycle_event
- art-158 run_emir_reporting_fit Record each verdict and execution_hash. Confirm zero network requests during each call.
- Call verify_execution_hash on mcp.ainumbers.co for each artifact, sending ONLY the artifact (policy_parameters + output_payload as emitted by the page). State whether every recompute matches.
- Call build_evidence_pack with the four hashes, labelled by node, plus the four kernel_digest values from chaingraph.json.
- Call anchor_batch on anchor.ainumbers.co with the four hashes and the pack digest. Use two authorities: Sigstore TSA and OpenTimestamps.
- Build the ledger fragment link for the art-158 artifact and open it. Report the verify chips.
- Write the cover note for the trade repository: which checks ran, on which kernel versions, that the report content never left the workstation, and how a supervisor re-verifies with no access to us (ledger link + anchor receipt + kernel_digest).
Finish by stating the execution_hash you received and the ledger link a human can verify it at.
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 · 25 lines · 29 tokens per session scan A ab06904f245f
zero-egress-emir-proof is a command published in the GitHub repository PostOakLabs/ainumbers (5 stars, last pushed yesterday), licensed MIT. It adds 29 tokens to every session and 384 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-09-06.
Other commands, from other repositories
monitor
AML transaction monitoring and suspicious activity reporting.
risk
Risk reassessment with updated due diligence.
screen
Comprehensive sanctions and PEP screening.
onboard
Customer onboarding with Step 0 verification (HITL consent required).
onboard-interactive
Interactive customer onboarding with Step 0 independent verification (dialog-based, 17 stagegates).
refresh
Periodic customer review with independent verification.