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.
npx agentmods add skills/huzaifa525/claude-code-optimizer/debug-errornpx skills add huzaifa525/claude-code-optimizer --skill debug-errorgit clone --depth 1 https://github.com/huzaifa525/claude-code-optimizerWhat 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 | $0.00025 | $0.00406 |
| Opus 5 | $0.00013 | $0.00203 |
| Sonnet 5 | $0.00005 | $0.00081 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
debug-error 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
Debug and fix: $ARGUMENTS
Steps
-
Parse the error
- Identify error type (runtime, compile, type, network, etc.)
- Extract file paths and line numbers from stack trace
- Identify the error message
-
Find the source
- Read the file(s) mentioned in the stack trace
- If no stack trace, Grep for the error message in codebase
- Read surrounding code to understand context
-
Trace the root cause
- Follow the call chain backwards
- Check recent git changes that might have caused it:
git log --oneline -10 git diff HEAD~3 - Look for common causes: null/undefined, wrong types, missing imports, race conditions
-
Implement the fix
- Fix the root cause, not just the symptom
- Handle edge cases that led to the error
-
Verify
- Run the failing scenario
- Run related tests
- Check for similar patterns elsewhere:
grep -r "similar_pattern" src/
-
Report
## Bug Fix Report ### Error [original error] ### Root Cause [why it happened] ### Fix [what was changed and why] ### Files Modified - [file] — [change] ### Verified - [how it was tested]
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 First seen · 65 lines · 25 tokens per session scan A 5bc744edd8e9
debug-error is a skill published in the GitHub repository huzaifa525/claude-code-optimizer (9 stars, last pushed 5mo ago), licensed MIT. It adds 25 tokens to every session and 406 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 skills, from other repositories
throughline
Use when the user asks to use Throughline from Codex, continue or restore Throughline memory, export read-only handoff context for a local launcher, prepare a new Codex thread handoff, summarize a captured Codex session, or check whether the Throughline Codex Stop hook captured the current session. Hide long…
critical-review
Use when you want structured feedback on a plan or document before implementation.
save
Save all session progress to status tracking files. Use when you want to checkpoint work mid-session or before ending.
code-review
Use when you want a thorough code review of files, changes, or the entire project before shipping.
implement-batch
Use when you want to implement the next batch of a plan. Handles module implementation, testing, and validation.
audit-orchestrator
Universal Pre-Scan → Analysis → Optimization → Report orchestrator for ANY project type — web apps (Astro/SvelteKit/Next), infrastructure/homelab repos, CLI tools, libraries, backend services, monorepos, data/ML projects, docs. Self-detects project type and runs the matching analysis track. Session state lives in…