cost-review
Skill84 starsChanged 14 days agoMITView on GitHub
Use for the monthly cost review of the platform, to see where the compute and the storage money goes, per job, pipeline and table, and what to cut.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- bakhod1r/awesome-agentstheir own version, first seen Oct 15, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- bakhod1r/awesome-agents★ 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.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Read the billing and usage records of the period: compute per job and pipeline, storage per table.
- Distinctive: line 38
Never deletes a table, never stops a job, never changes a cluster: it proposes.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Cost review
The job: where the money goes, per job, per pipeline and per table, and what to do about it. It proposes, it stops and deletes nothing.
Input: the period, the last month by default.
Steps
- Read the billing and usage records of the period: compute per job and pipeline, storage per table.
- The top 10 jobs by cost, and what each one produces.
- The cost per run of each scheduled pipeline, against the previous period.
- The storage bill: what the storage costs per month, and the part spent on tables nobody reads. The list of those tables comes from the big-review skill.
- Idle spend: clusters and warehouses that ran with nothing to do, and jobs that ran for nobody.
- The spikes: which day, which job, and which change caused it.
- Proposals, each with the saving per month and the risk, in order of the saving.
- Give the result as one web page.
Output
One HTML file: the cost of the period on top, the top jobs, the cost per run, the storage bill, the idle spend, the spikes, and the proposals last.
Reads
- the billing and usage records, the run records, the query logs, the catalog
Writes
- the web page only
Never
- Never deletes a table, never stops a job, never changes a cluster: it proposes.
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.