agentleFS
zedarvateszedarvates/frugal-skills/skills/cost-estimator/SKILL.md

cost-estimator

Skill1 starsChanged 33 days agoMITView on GitHub

Instructions for estimating task resources and provider costs with a separately installed runtime. Use estimates for planning, then compare them with measured usage, hardware costs and current provider prices; estimates are not billed-cost guarantees.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Files
SKILL.md

cost-estimator — tokens · model · money · time

Package scope and prerequisites

This catalog ships instructions, not the executable runtime. Python modules, scripts, local services and optional tools named below must be installed separately from the upstream project. Check their availability before running commands; if they are missing, explain the prerequisite instead of claiming execution or results. The host agent may use model tokens while following these instructions.

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)       # estimated resource use; measure the actual run

Reuses tiered_router's token+$ model and adds a throughput model for time. Local and cloud tiers have different provider, hardware and operating costs. Check current prices and observed latency. The upstream estimator informs 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.