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 skills add PostOakLabs/ainumbers --skill air-gapped-helm-handovergit 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/skills/postoaklabs/ainumbers/air-gapped-helm-handover)<a href="https://agentmods.dev/skills/postoaklabs/ainumbers/air-gapped-helm-handover"><img src="https://agentmods.dev/badge/skills/postoaklabs/ainumbers/air-gapped-helm-handover/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/skills/postoaklabs/ainumbers/air-gapped-helm-handover"><img src="https://agentmods.dev/badge/skills/postoaklabs/ainumbers/air-gapped-helm-handover.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.00071 | $0.00798 |
| Opus 5.5 | $0.00028 | $0.00319 |
| Sonnet 5.5 | $0.00014 | $0.00160 |
| Haiku 4.5 | $0.00007 | $0.00080 |
Grade A, and why
air-gapped-helm-handover 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 15d 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.
How it starts
The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The agent runs Helm and a person releases a bundle anyone can verify
Run a CECL workflow on a loopback-only Helm daemon, hit the consent-tier boundary at evidence export, and cross-check the kernel against the public worker.
Prompt
You are connected to a local Helm daemon at 127.0.0.1:4173. Run a CECL allowance workflow end to end, prove it, and get the evidence out the only way the daemon allows.
- Call catalog.search with "cecl". Pick the quarterly allowance pack. Call workflow.describe and workflow.manifest_get; list the nodes, the gates, and the manifest digest.
- Call workflow.dry_run on it (declare the io.modelcontextprotocol/tasks extension). Poll tasks/get until status is completed. Report the execution_hash.
- Call workflow.run on the same pack. Poll to completion. Report the execution_hash and whether it equals the dry run's.
- Call artifact.get and then artifact.verify on the real run. Report the per-step digests and the replay verdict.
- Attempt evidence.export with no ticket. Quote the error verbatim. Then tell me exactly what the human at the Helm UI has to do to mint a consent ticket, and wait for me to paste it.
- Once I paste the ticket, call evidence.export with it. Save the digest-level record.
- Cross-check the law: find the same kernel on mcp.ainumbers.co (find_tool "CECL allowance"), call it with the pack's sample inputs, and compare the kernel_digest and execution_hash to the Helm run. State whether the local daemon and the public worker agree.
- Call anchor_hash on the Helm run's execution_hash (Sigstore TSA). Return the receipt.
- Write the handover: what ran locally, what never left the machine, where the human consent sat in the flow, and how an auditor verifies the bundle offline with
helmd verify <bundle> --keys <publicKeys.json>and no network. If a named tool is not in your tool list, call call_tool with { "name": "", "arguments": { … } }. It runs the same validation and returns the same receipt.
How to run
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.
- 15d ago Changed 955d6f60f236
- 19d ago First seen · 49 lines · 71 tokens per session scan A 6ff05c00f4a8
air-gapped-helm-handover is a skill published in the GitHub repository PostOakLabs/ainumbers (11 stars, last pushed yesterday), licensed MIT. It adds 71 tokens to every session and 798 once invoked, about $0.0003 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-09-27.
Other skills, from other repositories
risk-assessment
Deterministic heuristic risk scoring using a four-factor weighted model (Geographic 30%, Customer 35%, Product 25%, Channel 10%) aligned with Basel III, EBA Guidelines, FATF standards, and FinCEN guidance. Bands: LOW (0-20), MEDIUM (21-60), HIGH (61-80), CRITICAL (81-100).
transaction-monitoring
AML transaction monitoring for ongoing customer relationships. Identifies suspicious patterns including structuring, layering, and unusual activity. Assesses against regulatory thresholds and prepares Suspicious Activity Reports (SARs) with HITL decision gates.
aws-cost-cleanup
Automated cleanup of unused AWS resources to reduce costs.
aws-security-audit
AWS security auditing — IAM users/roles/policies, CloudTrail API events, security posture analysis. Use when auditing IAM permissions, investigating security incidents, checking MFA compliance, or tracing API activity in CloudTrail.
japan-bav-und-corporate-pension-iorp
Japanisches betriebliches Altersversorgungssystem und IORP-Vergleich für europaeische Konzerne. Normen: IORP-II, japanisches Pensionsrecht DB-Pensions-Act. Prüfraster: Leistungsunterschiede, Finanzierungsanforderungen, Konvergenz. Output: Vergleichsanalyse Japan-bAV vs. EU-IORP. Abgrenzung: nicht Expatriate-Planung.
cis-aws-compute-2.4
Ensure an Organizational EC2 Tag Policy has been Created.