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/kbwen/agentic-os/systematic-debuggingnpx skills add KbWen/agentic-os --skill systematic-debugginggit clone --depth 1 https://github.com/KbWen/agentic-osWhat 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.00028 | $0.00431 |
| Opus 5 | $0.00014 | $0.00216 |
| Sonnet 5 | $0.00006 | $0.00086 |
| Haiku 4.5 | $0.00003 | $0.00043 |
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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- systematic-debugging — 100% identical, 0 lines differ
What it actually says
Systematic Debugging
Overview
The core of systematic debugging is: understand first, then fix. When encountering a bug, clarify symptoms, reproduction conditions, and blast radius. Draw hypotheses, verify them with experiments to isolate the root cause, and only then submit a minimal, verifiable fix.
Ironclad Rules
- No random patching: Do not submit fixes without root cause evidence.
- Change one variable at a time: Prevent unexplainable results from touching multiple areas at once.
- Fixes MUST include evidence: Include reproduction steps, verification, and regression results.
When to Use
- Hotfix incident response.
- Flaky tests.
- Cross-module anomalies that aren't intuitively obvious.
- Any "fixed but I don't know why" risk scenarios.
Four-Phase Process
Phase 1: Observe
- Precisely record error messages, timestamps, and input conditions.
- Create a Minimal Reproducible Example (MRE).
- Mark the blast radius (affected modules/users).
Phase 2: Hypothesize
- Propose 1–3 testable root cause hypotheses.
- Design "falsifiable" checks for each hypothesis.
- Prioritize high-probability, low-cost verifiable items.
Phase 3: Verify
- Run experiments and retain output logs.
- Adjust only one variable to confirm causality.
- Remove falsified hypotheses to converge on the most likely root cause.
Phase 4: Fix
- Implement a Minimal Fix.
- Add a Regression Test.
- Verify: The original error disappears AND existing behavior is not broken.
Common Mistakes
- Modifying code before reproducing the issue.
- Modifying too many files at once, failing to locate the effective fix point.
- Treating "accidental passes" as root cause resolved.
- Lacking regression tests, causing similar issues to happen again.
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.
- 2d ago First seen · 57 lines · 28 tokens per session scan A 62c160464493
systematic-debugging is a skill published in the GitHub repository KbWen/agentic-os (149 stars, last pushed 8d ago), licensed MIT. It adds 28 tokens to every session and 431 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-08-30.
Other skills, from other repositories
orloj-generator
Interactive scaffold generator for Orloj multi-agent systems. Use this skill whenever someone wants to create, set up, scaffold, bootstrap, or generate an Orloj agent system, pipeline, swarm, or hierarchy. Also trigger when users mention "orlojctl init", ask how to get started with Orloj, want to build a multi-agent…
muster-frappe-metadata
Design, generate, review, apply, and roll back Frappe or ERPNext metadata changes through Muster. Use for DocTypes, child tables, custom fields, property setters, workflows, roles, permissions, reports, print formats, web pages, workspaces, fixtures, patches, or installed-app compatibility.
muster-frappe-release
Build, seed, deploy, break, measure, and prove a Muster Frappe release. Use for bench or site setup, migrations, realistic ERPNext data, role matrices, browser/mobile QA, performance and recovery tests, release evidence, Frappeverse demos, or normal-speed presentation video.
muster-frappe-security
Threat-model and negatively verify Muster integrations with Frappe OAuth, multi-tenancy, RBAC, field permissions, agent delegation, channels, secrets, approvals, and audit logs. Use for identity linking, site registration, Telegram onboarding, policy changes, permission tests, or security release gates.
muster-frappe-workflows
Design and implement durable multi-step Muster workflows for Frappe with agent, subagent, and nested task graphs. Use for workflow definitions, planning, delegation, tool policies, approvals, retries, schedules, triggers, artifacts, dynamic page creation, or Claude-style universal JS and JSON automation.
muster-frappe-orchestrator
Coordinate end-to-end Muster automation work across Frappe or ERPNext architecture, metadata, UI, workflows, security, testing, deployment, and evidence. Use for cross-cutting features, production plans, multi-agent delivery, or work that spans Muster core and a Frappe app.