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 FutureJJ/claude-skills --skill debugging-detectivegit clone --depth 1 https://github.com/FutureJJ/claude-skillsWrote 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/futurejj/claude-skills/debugging-detective)<a href="https://agentmods.dev/skills/futurejj/claude-skills/debugging-detective"><img src="https://agentmods.dev/badge/skills/futurejj/claude-skills/debugging-detective/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/futurejj/claude-skills/debugging-detective"><img src="https://agentmods.dev/badge/skills/futurejj/claude-skills/debugging-detective.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00041 | $0.00187 |
| Opus 5.5 | $0.00016 | $0.00075 |
| Sonnet 5.5 | $0.00008 | $0.00037 |
| Haiku 4.5 | $0.00004 | $0.00019 |
Grade A, and why
debugging-detective 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 Detective
You are an expert in debugging detective focused on production-grade solutions.
Core Principles
- Follow industry best practices and proven patterns
- Optimize for maintainability and reliability
- Document decisions and trade-offs
- Measure before optimizing
Anti-Patterns
- Over-engineering simple solutions
- Ignoring error handling and edge cases
- Copying patterns without understanding context
- Premature optimization without profiling
Reference Guide
| Topic | Reference | Load When |
|---|---|---|
| Core patterns | references/patterns.md |
Common patterns and best practices |
| Advanced topics | references/advanced.md |
Complex scenarios and optimization |
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 · 29 lines · 41 tokens per session scan A a2cf34583b89
debugging-detective is a skill published in the GitHub repository FutureJJ/claude-skills (3 stars, last pushed 7mo ago), licensed MIT. It adds 41 tokens to every session and 187 once invoked, about $0.0002 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-31.
Other skills, from other repositories
quantum-debugger
Debugs complex, hard-to-reproduce issues: race conditions, memory leaks, deadlocks, performance regressions, heisenbugs, and crash analysis. Uses scientific debugging methodology with hypothesis generation, systematic testing, and root cause isolation. Use this skill when the user reports intermittent crashes…
offensive-bug-identification
Systematic bug identification methodology: source code review patterns, black-box testing strategies, taint analysis, dangerous function hunting, data flow tracing, and automated scanning setup. Use for code audits, bug bounty triage, or building vulnerability identification pipelines.
triage-issue
Verify an issue, persisted audit finding, or unresolved review finding against current code, classify it, and write only the contracted forge/ledger outcome. Supports independent batches and an immediate-fix review-finding route. Triggers: "triage-issue", "triage issue N", "triage this finding", "is this trigger met".
lynx-devtool
Use when working with Lynx DevTool or debugging a Lynx app, page, or device, especially when the task mentions clients or sessions, CDP or App commands, DOM/CSS inspection, runtime or console logs, evaluating JavaScript on a device, screenshots, heap snapshots, performance traces, Page.reload or App.openPage, global…
insforge-debug
Use when diagnosing problems in an InsForge project — reactive failures (SDK error object, HTTP 4xx/5xx, gateway timeout 502/503/504, edge function failure or timeout, login/OAuth/auth errors, RLS denial, realtime channel issues, slow query on one endpoint, edge function or Vercel deploy failure), proactive audits…
binary-re-dynamic-analysis
Use when you need to run a binary, trace execution, or observe runtime behavior. Runtime analysis via QEMU emulation, GDB debugging, and Frida hooking - syscall tracing (strace), breakpoints, memory inspection, function interception. Keywords - "run binary", "execute", "debug", "trace syscalls", "set breakpoint"…