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 helm-nightly-check-with-openclawgit 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/helm-nightly-check-with-openclaw)<a href="https://agentmods.dev/skills/postoaklabs/ainumbers/helm-nightly-check-with-openclaw"><img src="https://agentmods.dev/badge/skills/postoaklabs/ainumbers/helm-nightly-check-with-openclaw/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/helm-nightly-check-with-openclaw"><img src="https://agentmods.dev/badge/skills/postoaklabs/ainumbers/helm-nightly-check-with-openclaw.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.00551 |
| Opus 5.5 | $0.00020 | $0.00220 |
| Sonnet 5.5 | $0.00010 | $0.00110 |
| Haiku 4.5 | $0.00005 | $0.00055 |
Grade A, and why
helm-nightly-check-with-openclaw 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.
What it actually says
Helm nightly check with OpenClaw
Every night, recompute my extracts with helmd and post failures to my channel.
Prompt
Nightly loop for a paired helmd: recompute your packs and post only the failures.
- helmd catalog.search for each pack family you own (for example "2052a"); record the workflow ids and manifest digests.
- For each pack, helmd workflow.dry_run against today's extract files. Record any dry-run gate failures; those are your input problems, fix them before the real run.
- helmd workflow.run each pack for real. Poll helmd artifact.get for each run's execution_hash and per-step digests.
- helmd artifact.verify each run against its manifest digest. Classify: VERIFIED, FAILED, or STALE (digest drifted from yesterday).
- Compare each execution_hash with yesterday's note. A hash that changes when the extract did not change is your top alarm; quote the changed step.
- Give me the per-pack table: workflow id, digest, execution_hash, class.
- Write the nightly note for your channel: failures first, then the table, then the one command a teammate runs on their own helmd to reproduce any line. State plainly that nothing here required trusting your machine: every line re-verifies from the manifest digest. 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
Connect an MCP-capable host to https://mcp.ainumbers.co/mcp, then give the prompt above to the assistant.
Use synthetic inputs only. Never paste personal or production data.
Verify what came back
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 cdb4e13700ef
- 19d ago First seen · 39 lines · 49 tokens per session scan A a1009ebfb209
helm-nightly-check-with-openclaw is a skill published in the GitHub repository PostOakLabs/ainumbers (11 stars, last pushed yesterday), licensed MIT. It adds 49 tokens to every session and 551 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-09-27.
Other skills, from other repositories
implementing-aws-config-rules-for-compliance
Implementing AWS Config rules for continuous compliance monitoring of AWS resources, deploying managed and custom rules aligned to CIS and PCI DSS frameworks, configuring automatic remediation with SSM Automation, and aggregating compliance data across accounts.
hr-devops
Help HR managers, recruiters, and talent acquisition teams understand DevOps, Platform Engineering, Site Reliability Engineering (SRE), cloud infrastructure, CI/CD, and modern software delivery workflows. Use when asked to explain DevOps, screen DevOps candidates, understand CI/CD, compare DevOps and SRE, evaluate…
supply-chain-attack-response
Detect, respond to, and prevent software supply chain attacks on package registries, container images, and CI/CD pipelines with lockfile auditing, provenance verification, and emergency response playbooks.
llmops-platform-engineering
Build production LLMOps platforms with CI/CD, model promotion workflows, evaluation gates, rollback, and governance across cloud and self-hosted inference.
blue-green-deploy
Configure zero-downtime deployment strategies including blue-green, canary, and rolling deployments. Implement traffic shifting, health checks, and rollback procedures. Use when implementing production deployment strategies or zero-downtime releases.
aws-iam
Manage IAM users, roles, and policies. Implement least-privilege access and security best practices. Use when configuring AWS identity and access management.