cost-audit
Skill16 starsChanged 17 days agoMITView on GitHub
The optimizer's method for finding cost and waste in the agent workflow - model tier per agent, context loaded per step, redundant and skipped steps, slow or useless checks - and proposing ranked, reversible cuts. Use monthly, on a spend jump, or when the founder asks why something was slow or expensive.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- cordanaLLM/praetortheir own version, first seen Nov 1, 2026
- kovaa-dev/skillstheir own version, first seen Nov 1, 2026
- drvoss/everything-copilot-clitheir own version, first seen Oct 26, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- drvoss/everything-copilot-cli★ 49same name
- cordanaLLM/praetor★ 0same name
- kovaa-dev/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository120 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/agent-agentic-workflow.mdcCursor rule
- .cursor/rules/agent-android-dev.mdcCursor rule
- .cursor/rules/agent-architect.mdcCursor rule
- .cursor/rules/agent-backend-dev.mdcCursor rule
- .cursor/rules/agent-dashboard.mdcCursor rule
- .cursor/rules/agent-debugger.mdcCursor rule
- .cursor/rules/agent-desktop-dev.mdcCursor rule
- .cursor/rules/agent-devops.mdcCursor rule
- .cursor/rules/agent-explainer-writer.mdcCursor rule
- .cursor/rules/agent-feasibility.mdcCursor rule
- .cursor/rules/agent-growth.mdcCursor rule
- .cursor/rules/agent-ios-dev.mdcCursor rule
- .cursor/rules/agent-legal.mdcCursor rule
- .cursor/rules/agent-optimizer.mdcCursor rule
- .cursor/rules/agent-orchestrator.mdcCursor rule
- .cursor/rules/agent-platform-architect.mdcCursor rule
- .cursor/rules/agent-platform-designer.mdcCursor rule
- .cursor/rules/agent-product-designer.mdcCursor rule
- .cursor/rules/agent-qa.mdcCursor rule
- .cursor/rules/agent-researcher.mdcCursor rule
- .cursor/rules/agent-reviewer.mdcCursor rule
- .cursor/rules/agent-rollback.mdcCursor rule
- .cursor/rules/agent-security.mdcCursor rule
- .cursor/rules/agent-setup.mdcCursor rule
- .cursor/rules/agent-social-media.mdcCursor rule
- .cursor/rules/agent-web-dev.mdcCursor rule
- .cursor/rules/skill-bug-fix.mdcCursor rule
- .cursor/rules/skill-commit.mdcCursor rule
- .cursor/rules/skill-context-budget.mdcCursor rule
- .cursor/rules/skill-cost-audit.mdcCursor rule
- .cursor/rules/skill-decision-log.mdcCursor rule
- .cursor/rules/skill-experiment.mdcCursor rule
- .cursor/rules/skill-founder-voice.mdcCursor rule
- .cursor/rules/skill-frontend-design.mdcCursor rule
- .cursor/rules/skill-gates.mdcCursor rule
- .cursor/rules/skill-grilling.mdcCursor rule
- .cursor/rules/skill-handoff.mdcCursor rule
- .cursor/rules/skill-human-design.mdcCursor rule
- .cursor/rules/skill-human-steps.mdcCursor rule
- .cursor/rules/skill-karpathy-guidelines.mdcCursor rule
- .cursor/rules/skill-known-reds.mdcCursor rule
- .cursor/rules/skill-legal-review.mdcCursor rule
- .cursor/rules/skill-new-feature.mdcCursor rule
- .cursor/rules/skill-observability.mdcCursor rule
- .cursor/rules/skill-ordered-steps.mdcCursor rule
- .cursor/rules/skill-performance.mdcCursor rule
- .cursor/rules/skill-readiness-gate.mdcCursor rule
- .cursor/rules/skill-release.mdcCursor rule
- .cursor/rules/skill-requirement-first.mdcCursor rule
- .cursor/rules/skill-safe-data-write.mdcCursor rule
- .cursor/rules/skill-setup.mdcCursor rule
- .cursor/rules/skill-single-source.mdcCursor rule
- .cursor/rules/skill-spec-audit.mdcCursor rule
- .cursor/rules/skill-tailoring.mdcCursor rule
- .cursor/rules/skill-twin-check.mdcCursor rule
- .cursor/rules/skill-verified-claims.mdcCursor rule
- .cursor/rules/skill-verify-green.mdcCursor rule
- bug-fixSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
Checks: run time per check from the sweep output.
- Very specific: line 41
Never propose removing a gate, QA, security or legal review.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<!-- Generated by tools/sync_adapters.py from skills/cost-audit/SKILL.md. Edit the source, not this file. -->Cost audit
Gather (read only)
- Spend: whatever usage export the founder's tools give (per day, per model). If none
exists, say so and estimate from
docs/work/*/status.md(agents per feature, rounds per step), labelled as an estimate. - Shape: for the last few features, which agents ran, how many rounds each step took, how
many times work came back from
qa. - Context: the size of
AGENTS.md, every agent and skill file, and the documents agents read most.python tools/run_all.pyprints the files over budget. - Checks: run time per check from the sweep output; checks that have not failed in months.
Look for
- Savings counted before they were measured, such as prompt caching assumed in a cost table. Caches are specific to one provider and expire, so failover and low traffic both erase them.
- An agent on the deep tier doing checklist work, or a fast-tier agent whose work keeps coming back from review (too cheap is also waste).
- Work that went down the feature track and should have been a fix, or the reverse.
- Reviews repeated with no new input; parallel agents whose output was not used.
- Artifacts passed by content instead of path; whole files read where a grep would do.
- Shared files grown past budget.
- Rework: the costliest waste is a build that fails QA because the spec was thin. Sometimes the saving is more grilling, not less.
Propose
docs/cost/<YYYY-MM-DD>.md, one table, ranked by saving:
| Change | Saving (measured or estimated) | Risk to quality | How to undo | How we will know in two weeks |
Never propose removing a gate, QA, security or legal review. Proposing a cheaper way to run one
is fine. Each accepted proposal becomes an experiment (skills/experiment/).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

