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/kleosr/kleosrules/debuggingnpx skills add kleosr/kleosrules --skill debugginggit clone --depth 1 https://github.com/kleosr/kleosrulesWhat 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.00046 | $0.00396 |
| Opus 5 | $0.00023 | $0.00198 |
| Sonnet 5 | $0.00009 | $0.00079 |
| Haiku 4.5 | $0.00005 | $0.00040 |
Grade A, and why
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.
What it actually says
Bug hunt
No thin .mdc. This skill is the debugging roof.
Prove the cause; do not change code to generate hypotheses.
Mode
- Diagnose/assess → findings only.
- Fix requested → investigate first, then apply the smallest proven fix.
Workflow
- State the exact symptom, expected behavior, scope, and known-good baseline.
- Reproduce with the smallest deterministic case. Cannot reproduce → report the missing signal and stop.
- Read the complete error, logs, stack, inputs, and relevant state.
- Classify the likely boundary: logic, data, state, concurrency, cache, configuration, contract, environment, or integration.
- Trace backward from the first wrong observable value; compare failing and working paths.
- Write one falsifiable hypothesis and gather evidence for or against it.
- Inspect callers, contracts, and recent history when evidence points there.
- Prove the root cause before editing. After three misses, send STUCK with evidence and ask for the missing information.
- If authorized, fix one cause, add a regression test, and rerun the original reproduction plus affected TOOLCHAIN checks.
Guardrails
- No catch/sleep/retry, mock, assertion, or test weakening to hide failure.
- No simultaneous fixes for competing hypotheses.
- Cross-boundary symptoms use
NOW.md(/now). - Preserve logs/artifacts needed to explain the result; never expose secrets.
Report
Symptom → proven cause → evidence → changed or recommended fix → regression and original-repro results. Label anything unverified.
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 · 48 lines · 46 tokens per session scan A a0ca274a35c6
debugging is a skill published in the GitHub repository kleosr/kleosrules (2 stars, last pushed 2d ago), licensed MIT. It adds 46 tokens to every session and 396 once invoked, about $0.0002 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
coding-agents-hooks-authoring
To author, register, and test Rosetta hooks, add a SemanticKind, or debug a hook that won't fire.
agentic-dns
Agentic AI-native multi-tier DNS routing, live packet tracing, and failover bypass engine for Pi-hole, CoreDNS, dnsdist, Unbound, Stubby, DNSCrypt-Proxy, and VPN DNS.
diagnose
Diagnose your Claude Code hooks setup. Checks which hooks are active, verifies permissions, and identifies common configuration issues.
audit-credentials
Audits local credential setup for security compliance and produces a report. Use this skill when the user needs to: Check whether their credentials are properly stored and not leaking Validate credential rotation age against their policy Scan shell history, dotfiles, and git repos for exposed credentials Check file…
142-java-functional-programming
Use when you need to apply functional programming principles in Java — including writing immutable objects and Records, pure functions, functional interfaces, lambda expressions, Stream API pipelines, Optional for null safety, function composition, higher-order functions, pattern matching for instanceof and switch…
144-java-data-oriented-programming
Use when you need to apply data-oriented programming best practices in Java — including separating code (behavior) from data structures using records, designing immutable data with pure transformation functions, keeping data flat and denormalized with ID-based references, starting with generic data structures…