agentleFS
zedarvateszedarvates/botte-secrete/skills/cost_estimator/SKILL.md

cost_estimator

Skill2 starsChanged 3 months agoMITView on GitHub

Estimate what a task or a fix will cost — tokens, model/tier, money ($), and wall-time — using the tiered cost model. Use whenever the user wants to know the cost of a correction, audit, or task before running it, or to compare local vs cloud cost.

The file

Files
SKILL.md

cost_estimator — tokens · model · money · time

from skills.cost_estimator import estimate, estimate_fix
estimate("code_review", 4000).human()    # "2000 tok · Haiku/Flash (cloud) · $0.0001 · ~16s"
estimate_fix("dead_code", count=11)       # local · free · ~34s

Reuses tiered_router's token+$ model and adds a throughput model for time. Local tiers are free (slower/token); cloud tiers are billed (faster). Powers the fix plan and any "what will this cost?" question. Exposed via [[llm_mcp]] as estimate_cost. Related: [[fix]], [[auto_router]], [[metrics]].

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.