Borrowing it
Nothing to install: this file belongs to ldayton/Dippy. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ldayton/Dippy/main/.claude/skills/debug/SKILL.mdgit clone --depth 1 https://github.com/ldayton/DippyWrote 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/ldayton/dippy/debug)<a href="https://agentmods.dev/skills/ldayton/dippy/debug"><img src="https://agentmods.dev/badge/skills/ldayton/dippy/debug/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/ldayton/dippy/debug"><img src="https://agentmods.dev/badge/skills/ldayton/dippy/debug.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00010 | $0.00222 |
| Opus 5.5 | $0.00004 | $0.00089 |
| Sonnet 5.5 | $0.00002 | $0.00044 |
| Haiku 4.5 | $0.00001 | $0.00022 |
Grade A, and why
debug 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 1mo 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
Debug a Dippy issue based on user-provided context.
The user will provide:
- The command that was incorrectly approved or blocked
- Expected vs actual behavior
- Any relevant error messages or logs
Process
- Understand the bug from the provided context
- Search the codebase to find the relevant handler or pattern
- Write a failing test FIRST in the appropriate test file
- Run
just testand verify the test fails as expected - Fix the bug in the handler or pattern
- Run
just testuntil the test passes
Finish
When tests pass:
uv run ruff check --fix && uv run ruff format
just check MUST pass before you're done.
Restrictions
- ONLY modify files directly related to the bug
- Make minimal, targeted fixes
- Do NOT refactor or "improve" unrelated code
- Do NOT create a git commit or PR
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.
- 1mo ago First seen · 38 lines · 10 tokens per session scan A 48f07c2450ee
debug is a skill published in the GitHub repository ldayton/Dippy (243 stars, last pushed 4mo ago), licensed MIT. It adds 10 tokens to every session and 222 once invoked, about $0.0000 per session on Opus 5.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
claw-admin
Claw system administration: service management, IM connections, logs, cron, and workspace diagnostics. Use when the user asks to manage claw services, connect/disconnect IM platforms, view logs, or perform system-wide operations.
optimize
Review code for efficiency and performance. Triggered by "/optimize" when user wants to identify bottlenecks or improve performance.
longline-repo-allowlist
Use when scoping allow/ask rules for a command family (kubectl, oc, terraform, aws, gcloud, docker, etc.) to one repository so routine invocations stop prompting only inside that repo. Triggers include "allow kubectl in this repo", "stop asking about X commands", "add longline rules for this project", "allowlist…
code_explorer
Explores the repository to locate primary source files, coupled UI components, and test files for bug reports or feature requests.
test-failure-explorer
Import and query an existing Vitest 3.2 JSON report to explore test failures, file-level errors and original diagnostic evidence.
session-investigator
Investigate fast-agent session and history files to diagnose issues. Use when a session ended unexpectedly, when debugging tool loops, when correlating sub-agent traces with main sessions, or when analyzing conversation flow and timing. Covers session.json metadata, history JSON format, message structure, tool…