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 kensaurus/cursor-kenji --skill audit-infra-costgit clone --depth 1 https://github.com/kensaurus/cursor-kenjiWrote 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/kensaurus/cursor-kenji/audit-infra-cost)<a href="https://agentmods.dev/skills/kensaurus/cursor-kenji/audit-infra-cost"><img src="https://agentmods.dev/badge/skills/kensaurus/cursor-kenji/audit-infra-cost/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/kensaurus/cursor-kenji/audit-infra-cost"><img src="https://agentmods.dev/badge/skills/kensaurus/cursor-kenji/audit-infra-cost.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.00081 | $0.01322 |
| Opus 5 | $0.00041 | $0.00661 |
| Sonnet 5 | $0.00016 | $0.00264 |
| Haiku 4.5 | $0.00008 | $0.00132 |
Grade A, and why
audit-infra-cost 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 6d 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
audit-infra-cost — Hosting spend without hurting reliability
Degree of freedom: HIGH — quantify and plan. Phase 2 stays plan-only
until approved. Never propose a cut that weakens backups (plan-backup-dr).
Read-only. Find where money leaks in the infra bill and plan cuts that do not trade away reliability.
For a solo operator, infra cost is runway. A silent egress or storage leak can double a bill nobody is watching.
Quantify and plan. Apply only on approval. Never propose a cut that weakens backups (
plan-backup-dr) or user experience.
This skill vs neighbors
| Skill | Owns |
|---|---|
| audit-infra-cost (this) | Compute, storage, bandwidth, platform fees |
audit-cicd |
GitHub Actions minutes / artifacts |
plan-llm-cost-guardrails |
Model tokens / quota abuse |
test-load |
Measured peak — right-size to this, not a guess |
audit-bundle-size / audit-performance |
Client payload (feeds egress) |
backend-db-performance |
The index that stops compute burn |
How to reason
- Observe — billed resource, pricing model, and (if exposed) the breakdown line
- Interpret — is this utilization, a leak (egress/storage/zombies), or a tier mismatch?
- Classify — safe quick win / medium / structural / do-not-cut (backup/UX)
- Severity — by $ magnitude × reliability risk, not by how easy the cut looks
Worked example
Observe: object-storage bill is 40% of spend; logs prefix has no lifecycle; backups retained 90 days (DR requirement). Interpret: unbounded logs are the leak; backup retention is not a cut. Classify: safe quick win (expire temp logs) + do-not-cut (backups). Severity: major $; reliability risk low if only temp logs expire. Finding: logs | ~X% | lifecycle 7d | do not touch backup prefix
Phase 0 — Map the spend surface [HIGH freedom]
Enumerate billed resources and, if the provider exposes it, the breakdown:
- Compute (functions / servers / containers)
- Database (compute + storage + connections)
- Object storage (GB + operations)
- Egress (usually the sneaky line)
- CDN, per-seat / per-project fees
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.
- 6d ago First seen · 140 lines · 81 tokens per session scan A 64dba65260eb
audit-infra-cost is a skill published in the GitHub repository kensaurus/cursor-kenji (9 stars, last pushed 11d ago), licensed MIT. It adds 81 tokens to every session and 1,322 once invoked, about $0.0004 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-03.
Other skills, from other repositories
yc-batch-evaluator
Evaluate YC batch companies for investment — scrapes the YC directory, researches each company and its founders (work history, LinkedIn, website), assesses founder-company fit, and exports to Google Sheets with priority rankings. Use when asked to evaluate YC companies, research a YC batch, screen startups, or do due…
company-funding-search
Find company funding history, investors, and investment details.
uptime-monitor
Monitor website uptime - check availability, response times, and status.
cost-optimization
Audit and reduce infrastructure and tooling costs without sacrificing reliability or velocity. Use this skill when reviewing monthly cloud or SaaS spend, finding unused resources, rightsizing infrastructure, negotiating vendor contracts, deciding what to consolidate, or planning for budget cuts. Triggers on cost…
802-regulations-dora
Use when reviewing, designing, or modifying Java enterprise systems that may support financial entities, critical ICT services, third-party ICT provider integrations, or operational resilience obligations under DORA. This should trigger for requests such as Review a Java platform for DORA ICT risk controls; Design…
pier-cloud
This skill should be used when the user needs to consume the Pier Cloud (Lighthouse) API for cloud cost management — including JWT authentication, listing contexts, workspaces, and FinOps data views. Trigger whenever there is a need to integrate, automate, or debug calls to the Pier Cloud platform via Python, Node.js…