agentleFS
ThomasLangbroekThomasLangbroek/frugal/skills/router-stats/SKILL.md

router-stats

Skill37 starsChanged 4 months agoMITView on GitHub

Report frugal routing metrics - cost per agent tier, escalation rate, and estimated savings versus running everything on the top-tier model.

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
  1. Distinctive:

    Run the report and show its output verbatim as markdown:

    line 7
  2. Distinctive:

    After the table: if any agent's escalation count exceeds 20% of its runs, point at the routing decision table row that routes to it and …

    line 15

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Run the report and show its output verbatim as markdown:

python3 "<plugin-root>/scripts/stats.py"

<plugin-root> is two directories up from this skill's base directory (the base directory is announced when this skill loads). Pass --path <file> only if the user names a different metrics file.

After the table: if any agent's escalation count exceeds 20% of its runs, point at the routing decision table row that routes to it and suggest moving that task type one tier up.

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.