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/plugins/postoaklabs/ainumbers/claude-plugin)<a href="https://agentmods.dev/plugins/postoaklabs/ainumbers/claude-plugin"><img src="https://agentmods.dev/badge/plugins/postoaklabs/ainumbers/claude-plugin/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/plugins/postoaklabs/ainumbers/claude-plugin"><img src="https://agentmods.dev/badge/plugins/postoaklabs/ainumbers/claude-plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
ainumbers 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 2d 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
{
"author": {
"name": "Post Oak Labs"
},
"description": "Deterministic regulatory-computation estate: 640+ compliance tools, chains, a verify ledger, and a timestamping anchor, callable over MCP with zero-egress in-page twins.",
"homepage": "https://ainumbers.co",
"license": "CC-BY-4.0",
"name": "ainumbers",
"version": "1.0.0"
}
What it installs
The manifest is a name and a version. 1 skill, 5 commands travel with it, and installing the plugin installs all of them — 151 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 2d ago First seen · 11 lines scan A f15df40165c7
ainumbers is a plugin published in the GitHub repository PostOakLabs/ainumbers (5 stars, last pushed today), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
compliance
US securities regulatory guidance for broker-dealers and investment advisers. Covers FINRA, SEC, ERISA, FinCEN, and CFA Institute GIPS requirements. Guidance-only — no Python scripts.
us-sox
Sarbanes-Oxley Act of 2002 (SOX) — Reference-depth plugin for ICFR scoping, IT General Control (ITGC) testing, and §302/§404/§906 evidence preparation. Frames SOX as the governance layer over ICFR; security work flows in via ITGCs and SOC 1 reliance on vendor systems.
glba
GLBA Plugin - Gramm-Leach-Bliley Act for financial institutions with Safeguards Rule and Privacy Rule compliance.
us-finra
FINRA Plugin - Broker-dealer cybersecurity guidance (builds on SEC Reg S-P, SEC 17a-4).
kyc-analyst
KYC/AML compliance automation with mandatory Step 0 independent verification, 17 stagegates, deterministic risk scoring, Excel dashboards, PDF reports, and immutable audit trails for UK/EU/MENA/US jurisdictions.
geldwaesche-aml-kyc
Geldwäsche- und Terrorismusfinanzierungs-Prävention aus deutscher Praxisperspektive – GwG-Risikoanalyse § 5 (Methodik, Risikokategorien, Aktualisierung), KYC-Identifikationspflicht §§ 10 ff. mit wirtschaftlich Berechtigtem §§ 3 ff. und Transparenzregister, Verdachtsmeldung an die FIU § 43 inklusive § 46…