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 Bidiche49/claude-conf --skill debug-forensicgit clone --depth 1 https://github.com/Bidiche49/claude-confWrote 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/bidiche49/claude-conf/debug-forensic)<a href="https://agentmods.dev/skills/bidiche49/claude-conf/debug-forensic"><img src="https://agentmods.dev/badge/skills/bidiche49/claude-conf/debug-forensic/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/bidiche49/claude-conf/debug-forensic"><img src="https://agentmods.dev/badge/skills/bidiche49/claude-conf/debug-forensic.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.00077 | $0.04006 |
| Opus 5.5 | $0.00031 | $0.01602 |
| Sonnet 5.5 | $0.00015 | $0.00801 |
| Haiku 4.5 | $0.00008 | $0.00401 |
Grade A, and why
debug-forensic 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.
How it starts
The opening of the file, as written. The whole thing — 298 lines — stays where its author put it; the contents beside it link to each section on GitHub.
debug-forensic — Recadrage forensique d'une session de debug
Ton role : transformer une investigation qui derive (accumulation d'hypotheses, lecture de plus en plus de fichiers, "ca pourrait etre X ou Y") en une posture forensique stricte. Tu produis soit (a) un prompt a coller dans une session vierge, soit (b) un bloc de recadrage a injecter dans la conv courante.
Posture imposee au prompt produit : donnees > inference > UNE hypothese > UN test decisif > STOP. Pas de speculation, pas de refactor preventif, pas de "lire tout le repo".
Etape 1 — Detecter le mode
Diagnostique la conversation courante avant toute autre action.
| Signal | Mode |
|---|---|
| Conv contient deja des logs concrets, des hypotheses testees, des fichiers lus, des eliminations explicites | AUTO-EXTRACT |
| Conv neuve, ou bug juste mentionne sans investigation | INTERVIEW |
Argument new passe au skill |
force INTERVIEW |
Argument here passe au skill |
force la sortie en bloc de recadrage (pas de nouvelle conv) |
Annonce le mode detecte en UNE ligne : Mode: AUTO-EXTRACT — j'ai trouve N donnees factuelles et M eliminations dans la conv.
Etape 2 — Collecter le contexte
Mode AUTO-EXTRACT
Scanne la conversation et extrait :
- Symptome exact : ce qui est observe (ex: "freeze + hot restart impossible apres push de MaterialPageRoute X").
- Donnees ground-truth : logs precis, traces, comportement reproductible. UNE phrase factuelle par donnee.
- Eliminations : hypotheses deja testees ET invalidees, avec la preuve (ex: "ce n'est pas la memoire — heap stable a 80MB pendant le freeze").
- Fichiers deja lus : chemins exacts.
- Zones suspectes restantes : ce qui n'a pas encore ete teste mais qui pourrait causer le bug.
- Plateforme / stack / version : iOS 17.4, Flutter 3.22, Dart 3.4, etc.
Si une donnee critique manque (logs absents, repro non confirmee, version inconnue), groupe toutes les questions en UN SEUL message plutot que de poser plusieurs questions a la suite.
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 · 298 lines · 0 tokens per session scan A 4a1cb13a53c4
debug-forensic is a skill published in the GitHub repository Bidiche49/claude-conf (2 stars, last pushed 5mo ago), licensed MIT. It adds 77 tokens to every session and 4,006 once invoked, about $0.0003 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
atomic-debug
Hypothesis-driven debugging skill. Use when a bug, test failure, crash, or unexpected behavior is reported. Auto-trigger on error pastes or "broken/doesn't work/failing" language. Explicit invocation: /atomic-debug. Output: symptom statement → hypothesis table → cheapest test first → root cause. No symptom-patching.…
sipcode-regress
Check the user's own local Claude Code and Codex logs for regressions after an update (prompt-cache misses, 5-minute cache TTL, uncached context, hourly cache rebuilds, Codex usage limit draining faster per token) and pin each one to the version that introduced it, using the Sipcode CLI. Use when the user asks whether…
config-manager
Skill that manages configuration.
code-review-helper
A safe skill that helps with code review tasks.
system-admin-helper
Skill with dangerous system commands.
ralphctl-debugging-and-error-recovery
Systematic root-cause debugging. Use when tests fail, builds break, something that worked before broke, or behaviour does not match expectations — when you need to figure out what broke and why. Follow stop-the-line → reproduce → localize → reduce → root-cause → guard-with-regression-test → verify, not guessing; the…