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-skillsWrote 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-skills/fix)<a href="https://agentmods.dev/commands/sagargupta16/claude-skills/fix"><img src="https://agentmods.dev/badge/commands/sagargupta16/claude-skills/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-skills/fix"><img src="https://agentmods.dev/badge/commands/sagargupta16/claude-skills/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.00011 | $0.00309 |
| Opus 5 | $0.00005 | $0.00154 |
| Sonnet 5 | $0.00002 | $0.00062 |
| Haiku 4.5 | $0.00001 | $0.00031 |
Grade A, and why
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 2d 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
Live state
- Branch: !
git rev-parse --abbrev-ref HEAD - Recent changes: !
git log --oneline -10 - Uncommitted diff: !
git diff
Task
Fix the bug described in $ARGUMENTS (or the most recent error output in the conversation).
Process:
- Parse the symptom. Read any stack trace bottom-up. Identify the exact file and line of the crash.
- Root-cause, not symptom. The crash site is often downstream of the real bug. Trace backwards:
- Where did the bad data originate?
- What contract was violated?
- Does a recent commit in the log above correlate?
- Minimal fix. Change only what's needed at the true root cause. Do not refactor adjacent code. Do not add unrelated improvements.
- Verify. Run the narrowest test that covers this behavior. If no test exists, write one that would have caught the bug.
- Report.
Output
SYMPTOM: <what breaks>
ROOT CAUSE: <file:line -- why>
FIX: <diff or summary>
VERIFICATION: <test run, pass/fail>
CONFIDENCE: <high | medium | low>
If confidence is low, list alternative hypotheses before applying.
$ARGUMENTS
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.
- 2d ago Changed 7a951a6116fc
- 8d ago First seen · 39 lines · 11 tokens per session scan A 5c60b4696913
fix is a command published in the GitHub repository Sagargupta16/claude-skills (5 stars, last pushed 2d ago), licensed MIT. It adds 11 tokens to every session and 309 once invoked, about $0.0001 per session on Opus 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-31.
Other commands, from other repositories
commit
Create a git commit with intelligent message drafting (-f for fast, -v for verbose).
review-arch
Review app architecture: components, data flows, risks, and prioritized improvements.
fire-resurrect
Autonomous Resurrection Mode — reverse-engineer intent from messy code, then rebuild clean from scratch.
fire-reflect
After any failure (debug resolution, test failure, approach rotation, stalled loop), capture what was tried, why it failed, and what actually worked as a persistent reflection. Future sessions search these before investigating.
fire-verify-uat
Conversational User Acceptance Testing with automatic parallel diagnosis on failures.
sruja-bugfix-triage
Systematic workflow for triaging and fixing bugs with architecture grounding.