cost-optimizer

Runs gated cost-reduction experiments on evaluated agents and writes eval/cost_report.md.

1|9|Updated Jul 11, 2026
One-click install
npx skills add https://github.com/agenticgogol/Edureka_Coding_Agent_Enabled_Demo_11Jul --skill cost-optimizer-agenticgogol
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cost-optimizer
Source: https://github.com/agenticgogol/Edureka_Coding_Agent_Enabled_Demo_11Jul/tree/main/.claude/skills/cost-optimizer
Command: npx skills add https://github.com/agenticgogol/Edureka_Coding_Agent_Enabled_Demo_11Jul --skill cost-optimizer-agenticgogol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reducing LLM eval and agent runtime costs is risky: swapping to a cheaper model, compressing prompts, or routing tasks can silently degrade quality, and savings measured against an uncalibrated judge are meaningless. This Skill enforces a calibrated-judge gate and runs controlled cost experiments so savings never come at the expense of undetected regressions. ## Core Features & Use Cases - Calibration Gate: Refuses to run unless eval/calibration_report.md shows an approved judge (kappa >= 0.6), directing users to judge-calibrator first. - Three Gated Experiments: Model substitution (per-task results against baseline), prompt compression (token savings always paired with score deltas), and a rule-based router tested against existing golden-set labels. - Structured Reporting: Writes eval/cost_report.md with cost/token deltas, aggregate and per-task score deltas, and adopt/reject recommendations per experiment. - Use Case: After running baseline-runner and judge-calibrator on an agent, ask to cut costs — the Skill re-runs the eval with a cheaper model, reports which tasks tolerate it, and recommends selective routing. ## Quick Start Ask the agent to reduce eval costs for the current project, for example by testing a cheaper model against the existing baseline and golden set.

Frequently Asked Questions about cost-optimizer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reduce LLM eval costs without losing quality?▼

Run controlled experiments against your existing baseline: substitute a cheaper model and compare per-task scores, compress prompts while tracking score deltas alongside token savings, or route simple tasks via rules. Always validate against the same golden set and graders.

How to test if a cheaper model works for my agent?▼

Re-run your eval with the cheaper model as the system under test and compare results per task, not in aggregate. Flag any task where the cheaper model regresses below the calibrated pass bar so routing can be selective rather than all-or-nothing.

Why does the cost optimizer refuse to run?▼

It refuses when eval/calibration_report.md is missing or shows kappa below 0.6 for affected metrics. An uncalibrated judge makes cost experiments untrustworthy, so you must run judge-calibrator first to establish an approved judge.

Can I measure prompt compression savings without re-running evals?▼

No. Token savings alone are meaningless without score deltas, so prompt compression requires re-running the eval against the same golden set. Metrics tied to trimmed content, like faithfulness or context recall, must be checked specifically.

What are the limitations of rule-based routing for cost savings?▼

The router only works for tasks already labeled as unambiguously simple in the existing golden set; it does not invent new simplicity heuristics. Its test set is the golden set itself, so coverage is limited to the categories your eval already labels.