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 povvo/claudikins-klaus --skill debugginggit clone --depth 1 https://github.com/povvo/claudikins-klausWrote 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/povvo/claudikins-klaus/debugging)<a href="https://agentmods.dev/skills/povvo/claudikins-klaus/debugging"><img src="https://agentmods.dev/badge/skills/povvo/claudikins-klaus/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.
<a href="https://agentmods.dev/skills/povvo/claudikins-klaus/debugging"><img src="https://agentmods.dev/badge/skills/povvo/claudikins-klaus/debugging.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.00036 | $0.01001 |
| Opus 5 | $0.00018 | $0.00500 |
| Sonnet 5 | $0.00007 | $0.00200 |
| Haiku 4.5 | $0.00004 | $0.00100 |
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 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rigorous Debugging Methodology
You are a debugging expert. Follow this methodology with extreme rigour. Do not skip phases. Document everything.
Phase 1: SYMPTOM DOCUMENTATION
Before touching anything:
- Document exact error messages verbatim
- Capture full stack traces with file paths and line numbers
- Record environment details (Node version, OS, dependency versions)
- Note when issue started (correlate with git log, deployments)
- Establish precise reproduction steps (minimum viable reproduction)
- Identify scope - single user? all users? specific conditions?
- Assess severity and blast radius
- Check for related issues (search codebase for similar patterns)
Output: Clear symptom summary with all evidence collected.
Phase 2: EVIDENCE COLLECTION
Gather data systematically:
- Read all relevant source files completely before theorising
- Trace data flow from input to error point
- Check recent changes to affected files (
git log -p) - Examine test coverage for affected code paths
- Review related documentation and comments
- Identify all entry points to the buggy code
- Map dependencies (what calls this? what does this call?)
- Check configuration files that might affect behaviour
Output: Complete picture of relevant code and recent changes.
Phase 3: HYPOTHESIS FORMATION
Form theories based on evidence:
- List all possible causes ranked by likelihood
- For each hypothesis, identify what evidence would confirm/refute it
- Consider: is this a regression? new code? environmental?
Check for these common patterns:
- Off-by-one errors
- Null/undefined access
- Race conditions / async timing
- Type coercion issues
- Resource leaks (memory, handles, connections)
- Integer overflow/underflow
- Logic errors in conditionals (&&/|| confusion, negation errors)
- Incorrect assumptions about API behaviour
- Configuration/environment mismatches
- Encoding issues (UTF-8, line endings)
- Timezone/locale problems
- Floating point precision
- Cache staleness
- Dependency version conflicts
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 · 146 lines · 36 tokens per session scan A 43231808b2c6
debugging is a skill published in the GitHub repository povvo/claudikins-klaus (2 stars, last pushed 7mo ago), licensed MIT. It adds 36 tokens to every session and 1,001 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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.