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 skills add poshan0126/dotclaude --skill debug-fixgit clone --depth 1 https://github.com/poshan0126/dotclaudeWrote 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/skills/poshan0126/dotclaude/debug-fix)<a href="https://agentmods.dev/skills/poshan0126/dotclaude/debug-fix"><img src="https://agentmods.dev/badge/skills/poshan0126/dotclaude/debug-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/skills/poshan0126/dotclaude/debug-fix"><img src="https://agentmods.dev/badge/skills/poshan0126/dotclaude/debug-fix.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 118 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00043 | $0.01207 |
| Opus 5.5 | $0.00017 | $0.00483 |
| Sonnet 5.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 1mo 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.
- 1mo ago First seen · 123 lines · 43 tokens per session scan A d4e4e70a3a90
debug-fix is a skill published in the GitHub repository poshan0126/dotclaude (870 stars, last pushed 1mo ago), licensed MIT. It adds 43 tokens to every session and 1,207 once invoked, about $0.0002 per session on Opus 5.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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
deck-retro
Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…