Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From Frugal
Reports frugal routing metrics including cost per agent tier, escalation rate, and estimated savings versus using top-tier model for all requests.
How this skill is triggered — by the user, by Claude, or both
Slash command
/frugal:router-statsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Run the report and show its output verbatim as markdown:
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.
npx claudepluginhub thomaslangbroek/frugal --plugin frugalGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Resolves in-progress git merge or rebase conflicts by analyzing history, understanding intent, and preserving both changes where possible. Runs automated checks after resolution.