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 agentmods add skills/cassianflorin/skill-hub-registry/systematic-debuggingnpx skills add CassianFlorin/skill-hub-registry --skill systematic-debugginggit clone --depth 1 https://github.com/CassianFlorin/skill-hub-registryWrote 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/cassianflorin/skill-hub-registry/systematic-debugging)<a href="https://agentmods.dev/skills/cassianflorin/skill-hub-registry/systematic-debugging"><img src="https://agentmods.dev/badge/skills/cassianflorin/skill-hub-registry/systematic-debugging.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00192 |
| Opus 5 | $0.00000 | $0.00096 |
| Sonnet 5 | $0.00000 | $0.00038 |
| Haiku 4.5 | $0.00000 | $0.00019 |
Grade A, and why
systematic-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 4d 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
Systematic Debugging
Use this skill when a command, test, build, service, or user workflow is failing.
Instructions
- Reproduce the exact symptom before proposing a fix.
- Capture the failing command, input, output, and environment assumptions.
- Trace from the symptom to the responsible code or configuration boundary.
- Form one hypothesis at a time and choose the smallest check that can disprove it.
- Change code only after the evidence points to a specific cause.
- After fixing, rerun the original failing check and a focused regression check.
Common Mistakes
- Treating a nearby warning as the root cause.
- Fixing code that was not exercised by the failing path.
- Using a broad green test suite as proof that the original symptom is fixed.
- Hiding uncertainty instead of naming the missing evidence.
Output Shape
- Symptom reproduced.
- Evidence trail.
- Root cause.
- Fix.
- Verification.
What ships with it
1 file 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.
- 4d ago First seen · 28 lines · 0 tokens per session scan A 48312e44fc59
systematic-debugging is a skill published in the GitHub repository CassianFlorin/skill-hub-registry (2 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 192 tokens. 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
simple_tool
A simple, safe skill that processes JSON configuration files.
google-sheets
Read, write, format, and analyze spreadsheet data through the Google Sheets API.
test-skill
A simple test skill for verifying the Tank registry E2E flow.
exfiltration_singlefile
Skill "exfiltration_singlefile" from tankpkg/tank, covering ssh key helper and usage.
injection_xml_tags
This skill demonstrates XML format injection.
skillsmith
Discover, install, compare, and manage Claude Code skills. Search the registry, get recommendations, validate skill quality, and manage your installed skills.