systematic-debugging

systematic-debugging is a skill for Claude Code, Codex from kimtth/agent-skill-100-lines-or-less. It costs 24 tokens per session (243 once invoked), scanned A, original, no licence file.

A structured guide for investigating unclear software bugs through testable explanations, called hypotheses. It uses a repeatable loop of checking evidence, making changes, and verifying results.

In plain words
What is it for?
Use it to investigate bugs whose causes are not immediately obvious and to verify each suspected fix.
Why use it?
It reduces random edits and helps narrow down the actual cause of a bug.

Skill for Claude CodeCodex

Which agent this was written for is unclear — body not stored (licence); the path alone says nothing.

Good fit Use it to investigate bugs whose causes are not immediately obvious and to verify each suspected fix.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/kimtth/agent-skill-100-lines-or-less/systematic-debugging
Install

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.

Any agent
npx skills add kimtth/agent-skill-100-lines-or-less --skill systematic-debugging
Clone the repo
git clone --depth 1 https://github.com/kimtth/agent-skill-100-lines-or-less

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for systematic-debugging

README.md
[![agentmods](https://agentmods.dev/badge/skills/kimtth/agent-skill-100-lines-or-less/systematic-debugging/github.svg)](https://agentmods.dev/skills/kimtth/agent-skill-100-lines-or-less/systematic-debugging)
Your own site
<a href="https://agentmods.dev/skills/kimtth/agent-skill-100-lines-or-less/systematic-debugging"><img src="https://agentmods.dev/badge/skills/kimtth/agent-skill-100-lines-or-less/systematic-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.

agentmods 80×15 button for systematic-debugging

Your own site · 80×15
<a href="https://agentmods.dev/skills/kimtth/agent-skill-100-lines-or-less/systematic-debugging"><img src="https://agentmods.dev/badge/skills/kimtth/agent-skill-100-lines-or-less/systematic-debugging.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 243 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00024 $0.00243
Opus 5 $0.00012 $0.00121
Sonnet 5 $0.00005 $0.00049
Haiku 4.5 $0.00002 $0.00024

Measured 8d ago against content hash 89dd408fa225, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

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 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.

skills/systematic-debugging/SKILL.md · 31 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

Changes

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.

  1. 8d ago First seen · 31 lines · 24 tokens per session scan A 89dd408fa225

Subscribe to this mod's changes

systematic-debugging is a skill published in the GitHub repository kimtth/agent-skill-100-lines-or-less (2 stars, last pushed 2mo ago), with no licence file. It adds 24 tokens to every session and 243 once invoked, about $0.0001 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-09-03.

Related

Other skills, from other repositories

spk-run-blocked-recovery

Recover from Spec Kitty blocked runtime states, missing artifacts, failed guards, stale worktrees, and decision-required loops.

Priivacy-ai/spec-kitty · 31 tokens

spk-admin-setup-doctor

Install, verify, and repair Spec Kitty commands, skills, agent paths, runtime prerequisites, and common setup failures.

Priivacy-ai/spec-kitty · 31 tokens

022-root-cause-analysis

Use when a framed problem needs root-cause investigation rather than a symptom-level fix, applying Five Whys, Fishbone (Ishikawa), Current Reality Tree, and constraint identification. This should trigger when an issue's Root Cause Analysis point of view needs evaluation, or when a maintainer directly asks to find the…

jabrena/plinth · 85 tokens

126-java-exception-handling

Use when you need to apply Java exception handling best practices — including using specific exception types, managing resources with try-with-resources, securing exception messages, preserving error context via exception chaining, validating inputs early with fail-fast principles, handling thread interruption…

jabrena/plinth · 144 tokens

skill-performance

AL performance optimization patterns for Business Central. Use when optimizing queries with SetLoadFields, working with FlowFields and CalcFields, profiling codeunits, or resolving performance issues.

javiarmesto/ALDC-AL-Development-Collection · 37 tokens

skill-debug

AL debugging and diagnostics for Business Central. Use when performing snapshot debugging, CPU profiling, analyzing telemetry, or troubleshooting runtime issues.

javiarmesto/ALDC-AL-Development-Collection · 28 tokens