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 HoangNguyen0403/agent-skills-standard --skill common-debugginggit clone --depth 1 https://github.com/HoangNguyen0403/agent-skills-standardWrote 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/hoangnguyen0403/agent-skills-standard/common-debugging)<a href="https://agentmods.dev/skills/hoangnguyen0403/agent-skills-standard/common-debugging"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/common-debugging/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/hoangnguyen0403/agent-skills-standard/common-debugging"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/common-debugging.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00029 | $0.00476 |
| Opus 5.5 | $0.00012 | $0.00190 |
| Sonnet 5.5 | $0.00006 | $0.00095 |
| Haiku 4.5 | $0.00003 | $0.00048 |
Grade A, and why
common-debugging 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 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.
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
Debugging Expert
Priority: P1 (HIGH)
Root-Cause Protocol
- OBSERVE: Gather error, logs, repro steps, recent diffs.
- REPRODUCE: Make the failure happen on demand or gather more evidence.
- HYPOTHESIZE: State one hypothesis in plain language.
- EXPERIMENT: Change one variable to prove or kill the theory.
- FIX: Touch code only after root cause proven.
- VERIFY: Re-run the failing case and regression checks.
Red Flags
- Stop if you are changing code before repro: You are guessing.
- Stop if fix #2 starts before understanding fix #1: Re-open root cause.
- Stop if "quick patch for now" appears: Symptom masking starts there.
Rationalization Prevention
- "The bug is obvious": Obvious bugs still need evidence.
- "I already tried a few things": That means you need structure.
- "It only fails in prod": Gather prod evidence, do not invent local myths.
- Minimal repro first: A minimal reproduction beats more random fixes.
Anti-Patterns
- No shotgun debugging: Prove root cause before changing code.
- No debug prints in production: Remove all print/console.log before commit.
- No symptom masking: Fix root cause; never swallow errors without handling.
References
Incident pressure checklist
- For production incidents, reproduce with a production-like replay and state one hypothesis before changing code; stop symptom patches until the root cause is proven.
Canonical response anchors
When this skill applies, preserve the following domain terminology or equivalent concrete examples in the answer when relevant:
-
hypothesis
-
one hypothesis
-
stop
-
Additional task-grounded exact anchors: minimal
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 61 lines · 29 tokens per session scan A 9701906d15c3
common-debugging is a skill published in the GitHub repository HoangNguyen0403/agent-skills-standard (583 stars, last pushed today), licensed MIT. It adds 29 tokens to every session and 476 once invoked, about $0.0001 per session on Opus 5.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-30.
Other skills, from other repositories
inspector-workbench
Runs Inspector UI work on the standalone Threads state lab so the agent can see the overlay. Use when a CopilotKit employee asks an agent to fix, polish, add, or debug Inspector UI, chrome, panes, overlay actions, launcher, Home, Threads, Playground, Memory, or any visual behavior in @copilotkit/web-inspector. Don't…
nextjs-idioms
Next.js App Router architecture: React Server Components (RSC), Server Actions, nested layouts, route handlers, and streaming. Use when building or refactoring Next.js web applications. Pair with react-idioms and typescript-idioms.
perf-optimization
Profile-driven performance optimization protocol. Use when profiling data (CPU, heap, trace) is available or when the user requests performance analysis. Covers methodology (Profile → Analyze → Opportunity Scan → Prioritize → Optimize → Benchmark), optimization pattern catalog, safety invariants, and when-to-stop…
incident-response
Structured incident workflow: severity classification, triage, diagnosis, mitigation, postmortem, and prevention. Template-driven with blameless review.
threejs
Build and debug 3D browser apps and games with Three.js or React Three Fiber: scene, materials, lighting, GLTF, physics, character controllers, cameras, post-processing, performance.
debug
Structured bug diagnosis and fixing workflow that reproduces, diagnoses root cause, applies a minimal fix, writes regression tests, and scans for similar patterns.