Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/Sagargupta16/claude-cost-optimizerWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/sagargupta16/claude-cost-optimizer/quick-fix)<a href="https://agentmods.dev/commands/sagargupta16/claude-cost-optimizer/quick-fix"><img src="https://agentmods.dev/badge/commands/sagargupta16/claude-cost-optimizer/quick-fix/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/sagargupta16/claude-cost-optimizer/quick-fix"><img src="https://agentmods.dev/badge/commands/sagargupta16/claude-cost-optimizer/quick-fix.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00010 | $0.00483 |
| Opus 5.5 | $0.00004 | $0.00193 |
| Sonnet 5.5 | $0.00002 | $0.00097 |
| Haiku 4.5 | $0.00001 | $0.00048 |
Grade A, and why
quick-fix scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 25d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Quick Fix
Apply a targeted bug fix with minimal token usage. No exploration, no discussion -- just fix.
Process
-
Identify: The user has described a bug or pointed to a specific file/line. If the file path is provided, read only the relevant section (use
offset/limitif possible). -
Fix: Apply the edit immediately. Do not:
- Explain the root cause in detail
- Show "before and after" comparisons
- Suggest related improvements
- Refactor surrounding code
- Read other files "for context"
-
Verify (only if a test command is known): Run the relevant test in one command. If no test file is obvious, skip this step.
-
Report: Respond with a single line describing the fix:
Fixed: {what was wrong} in {file path}
Rules
- ONE file edit per bug. If the fix truly requires multiple files, do them all in parallel in one turn.
- Do NOT read the entire file -- read only the area around the reported issue.
- Do NOT suggest follow-up improvements or "while we're here" changes.
- Do NOT explain the fix unless the user asks "why."
- If the bug description is ambiguous, ask ONE clarifying question -- do not guess.
Example
User: "The login button doesn't submit the form -- it's in src/components/LoginForm.tsx around line 45"
Good response:
[Reads lines 40-55 of LoginForm.tsx]
[Edits: changed type="button" to type="submit" on line 47]
Fixed: button type was "button" instead of "submit" in src/components/LoginForm.tsx
Bad response:
Let me take a look at the LoginForm component to understand the issue...
[Reads entire file]
I can see the problem! The button on line 47 has type="button" which prevents
form submission. This is a common issue in React forms because...
[Long explanation]
[Edit]
I've fixed the issue. The button was using type="button" instead of type="submit".
You might also want to consider adding form validation...
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 25d ago Changed 9caf43fb9eae
- 1mo ago First seen · 59 lines · 10 tokens per session scan A 4c6c6fa75509
quick-fix is a command published in the GitHub repository Sagargupta16/claude-cost-optimizer (40 stars, last pushed today), licensed MIT. It adds 10 tokens to every session and 483 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
fix-issue
A command that takes a GitHub Issue—a tracked bug, request, or question—and guides its fix from investigation through testing and submission. TDD means writing a failing test first, then changing the code until the test passes.
hotfix
An emergency software-fix workflow that moves directly from development to verification and Git commit, skipping the usual planning and design stages.
cleanup
A cleanup command that finds code, files, and dependencies that appear to be unused, then removes only items confirmed to be unnecessary.
fix
A command for fixing build, type-checking, and compilation errors with only the smallest necessary code changes. It covers common issues such as missing types, invalid imports, null values, configuration errors, and missing dependencies.
audit-agents-skills
Audit quality of agents, skills, and commands in a Claude Code project.
audit-repo-docs
Audit repository documentation against 85+ best practices from claude-code-ultimate-guide.