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 thomascasali/claude-kb-workflow --skill debugging-sistematicogit clone --depth 1 https://github.com/thomascasali/claude-kb-workflowWrote 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/thomascasali/claude-kb-workflow/debugging-sistematico)<a href="https://agentmods.dev/skills/thomascasali/claude-kb-workflow/debugging-sistematico"><img src="https://agentmods.dev/badge/skills/thomascasali/claude-kb-workflow/debugging-sistematico/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/thomascasali/claude-kb-workflow/debugging-sistematico"><img src="https://agentmods.dev/badge/skills/thomascasali/claude-kb-workflow/debugging-sistematico.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.00087 | $0.00745 |
| Opus 5 | $0.00044 | $0.00373 |
| Sonnet 5 | $0.00017 | $0.00149 |
| Haiku 4.5 | $0.00009 | $0.00075 |
Grade A, and why
debugging-sistematico 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 8d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debugging sistematico
Principio: la causa radice prima del fix. I fix sui sintomi falliscono.
Quando si attiva questa skill
- L'utente segnala un errore, eccezione, stack trace, test fallito, comportamento inatteso
- Una funzione "non funziona", "non parte", "dà errore"
- Sono già stati tentati 2+ fix senza successo → STOP e riparti dalla fase 1
- Una regressione (prima funzionava, ora no)
Le 4 fasi
1. Investigazione causa radice
Prima di proporre QUALSIASI fix:
- Leggi l'errore per intero (stack trace completo, non solo la prima riga)
- Riproduci il bug in modo consistente — se non lo riproduci, non lo hai capito
- Controlla i commit recenti (
git log --oneline -20,git diff HEAD~5) per identificare la regressione - Traccia il flusso dei dati a ritroso dall'errore fino alla sorgente
- Attraversa i confini di sistema: frontend → API → DB, app → servizio → log
2. Analisi del pattern
- Cerca un esempio funzionante simile nel codebase (
grepper pattern simili) - Confronta riga per riga le differenze
- Identifica le dipendenze (versioni pacchetti, env vars, config files, ordine di inizializzazione)
3. Ipotesi e test
- Formula UNA ipotesi specifica e falsificabile ("se cambio X, il bug sparisce perché Y")
- Testa cambiando UNA sola variabile alla volta
- Verifica il risultato prima di procedere
4. Implementazione
- Se possibile, scrivi prima un test che fallisce
- Applica UN fix che indirizzi la causa radice
- Verifica che il fix risolva il problema E che non rompa altro
Red flag che richiedono restart dalla fase 1
Se ti senti pensare:
- "Fix veloce per ora, indagine dopo"
- "Provo a cambiare X e vediamo"
- "Aggiungo un try/catch per nascondere l'errore"
- "Il problema sembra essere..." (senza prove)
→ Torna alla fase 1.
Stop rule
Se 3 fix consecutivi falliscono, ferma i tentativi e metti in discussione l'architettura o le tue assunzioni di base. È un sintomo di problema strutturale, non di bug isolato.
Anti-pattern da evitare
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.
- 8d ago First seen · 68 lines · 87 tokens per session scan A fa8b89b53235
debugging-sistematico is a skill published in the GitHub repository thomascasali/claude-kb-workflow (2 stars, last pushed 13d ago), licensed MIT. It adds 87 tokens to every session and 745 once invoked, about $0.0004 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
upstream-tracker
Manage upstream issue tracking for this project. Use when the user wants to log a bug or friction point in a vendor package or npm dependency, review open upstream items, resolve a tracked issue, run a trend review, generate the upstream observations section of a sprint retrospective, promote upstream observations to…
lint
Read-only audit of vault/wiki/ for structural and provenance drift. Reports Errors, Warnings, and Info per the lint rules in vault/CLAUDE.md. Trigger when the user says "lint the vault", "audit the wiki", "check for broken links", "run a health check on the wiki", or invokes /claude-wiki-pages:lint directly. Does not…
fix
Auto-repair what /claude-wiki-pages:lint reports. Idempotent — running twice on a clean tree produces no diff. Trigger when the user says "fix the lint errors", "repair the wiki", "auto-fix", or invokes /claude-wiki-pages:fix directly. Expects a fresh lint report in context, or runs its own lint pass internally.
status
One-command health check. Exercises every hook path and reports pass/fail per hook — without writing to vault/. Trigger when the user says "status", "health check", "is everything wired up", "did the install work", "dashboard", or invokes /claude-wiki-pages:status directly. Strictly read-only against vault content…
opencode-context-maintenance
Diagnose drift across the OpenCode + Obsidian context stack when vault notes, config, or host reality no longer align. Load when context feels stale or records disagree with reality. Do NOT use for triage, synthesis, or vault CRUD.
node-connect
Diagnose OpenClaw node connection and pairing failures for Android, iOS, and macOS companion apps. Use when QR/setup code/manual connect fails, local Wi-Fi works but VPS/tailnet does not, or errors mention pairing required, unauthorized, bootstrap token invalid or expired, gateway.bind, gateway.remote.url, Tailscale…