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/jerry0022/dotclaude/fixnpx skills add Jerry0022/dotclaude --skill fixgit clone --depth 1 https://github.com/Jerry0022/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.00102 | $0.01459 |
| Opus 5 | $0.00051 | $0.00730 |
| Sonnet 5 | $0.00020 | $0.00292 |
| Haiku 4.5 | $0.00010 | $0.00146 |
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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fix
Diagnose and fix the issue: $ARGUMENTS
Step 0 — Load Extensions
Check for optional overrides. Use Glob to verify each path exists before reading. Do NOT call Read on files that may not exist — skip missing files silently (no output).
- Global:
~/.claude/skills/fix/SKILL.md+reference.md - Project:
{project}/.claude/skills/fix/SKILL.md+reference.md - Merge: project > global > plugin defaults
Project extensions define framework-specific log paths (e.g., Electron logs in
%APPDATA%/<app>/logs/, Angular dev server console, etc.).
- Codex context: Read
{PLUGIN_ROOT}/deep-knowledge/codex-integration.md— this skill auto-invokes Codex on unclear root cause (§2 in that doc). Codex MUST be called via{PLUGIN_ROOT}/scripts/codex-safe.sh(5-min hard timeout, see "Hard Timeout & Failure-Tolerance" section), NEVER via the/codex:rescueAgent tool. Detect Codex availability now so Step 6 can act on it.
Step 1 — Triage: what broke?
If $ARGUMENTS is empty or vague, ask ONE focused question via AskUserQuestion:
- "Was ist passiert?" with options like: "Error in console", "Blank screen", "Crash on startup", "Wrong behavior"
- Do NOT ask multiple questions — get the symptom, then investigate.
Step 2 — Check recent changes first
The most common cause of bugs is recent code changes. Before reading logs:
git log --oneline -5
git diff HEAD~1 --stat
If the symptom appeared after a specific commit, focus investigation there.
Step 3 — Discover and read logs
Search for logs automatically — don't assume fixed paths:
Globfor**/*.logand**/logs/**in the project root- Check project extension for framework-specific log locations
- Read the most recent log file first — don't read all unless needed
Step 4 — Locate the failure point
Search for the error string via Grep. Follow the stack trace to the originating file and line.
Step 5 — Root cause analysis
Find the actual broken invariant — not just the symptom. Ask:
- What assumption is violated?
- What changed that broke this assumption?
- Is this a data issue, a logic issue, or a configuration issue?
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 · 128 lines · 102 tokens per session scan A 44618d261b3a
fix is a skill published in the GitHub repository Jerry0022/dotclaude (4 stars, last pushed 3d ago), licensed MIT. It adds 102 tokens to every session and 1,459 once invoked, about $0.0005 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
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…