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/poshan0126/dotclaude/debug-fixnpx skills add poshan0126/dotclaude --skill debug-fixgit clone --depth 1 https://github.com/poshan0126/dotclaudeWhat 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.00043 | $0.01207 |
| Opus 5 | $0.00022 | $0.00603 |
| Sonnet 5 | $0.00009 | $0.00241 |
| Haiku 4.5 | $0.00004 | $0.00121 |
Grade A, and why
debug-fix scanned grade A with 1 finding 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 3d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Find the simplest way to trigger the issue (a test, curl, script). How it starts
The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Find and fix the following issue:
Problem: $ARGUMENTS
Mode
Check $ARGUMENTS for --fast. Strip it before parsing the problem description.
- Default: careful debug-fix. Use when you have time to do this right.
- --fast: emergency hotfix. Use when production is broken and shipping speed matters more than thoroughness. Triggers a
hotfix/*branch from production, minimal-change discipline, critical-tests-only verification, and ships a[HOTFIX]PR. Before committing to fast mode, briefly confirm with the user that this is genuinely emergency-grade. If not, suggest dropping--fast.
Step 1: Understand
- Issue number:
gh issue view $ARGUMENTS(or the project's issue tracker). - Error or stack trace: parse it for file, line, error type, and call chain.
- Description: identify expected vs actual.
- URL or screenshot: examine the referenced resource.
If unclear, ask clarifying questions before proceeding.
Step 2: Hotfix branch (--fast only)
In --fast mode only:
- Detect the production branch:
git symbolic-ref refs/remotes/origin/HEADorgit remote show origin. - Stash uncommitted work if needed.
- Create and switch to
hotfix/<short-description>branched from production. - ASK the user to confirm the branch name first.
In default mode, skip this. Branch creation happens in Step 7.
Step 3: Reproduce (default only)
In --fast mode, skip this step. Trust the report and move to Step 5.
- Find the simplest way to trigger the issue (a test, curl, script).
- Confirm you can reproduce reliably.
- If you can't reproduce:
- Environment-specific? Check env vars, OS, runtime version, database state.
- Intermittent? Likely a race condition. Look for shared mutable state, timing dependencies, async ordering assumptions.
- Already fixed?
git logfor recent commits mentioning the issue.
Step 4: Investigate (default only)
In --fast mode, skip this and go to Step 5. Trust the report and minimize investigation depth.
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.
- 3d ago First seen · 123 lines · 43 tokens per session scan A d4e4e70a3a90
debug-fix is a skill published in the GitHub repository poshan0126/dotclaude (860 stars, last pushed 6d ago), licensed MIT. It adds 43 tokens to every session and 1,207 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…