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/ldayton/dippy/debugnpx skills add ldayton/Dippy --skill debuggit clone --depth 1 https://github.com/ldayton/DippyWhat 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.00010 | $0.00222 |
| Opus 5 | $0.00005 | $0.00111 |
| Sonnet 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 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
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.
- 2d 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 2mo ago), licensed MIT. It adds 10 tokens to every session and 222 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
toolpermit
Install, configure, operate, and troubleshoot ToolPermit, the local-first permission policy, one-time approval, and redacted audit layer for MCP stdio tool calls. Use when Codex needs to protect or inspect an MCP server, wrap an MCP stdio command, create or review allow/ask/deny policies, manage approvals, replay…
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-runner
安全代码执行（Python/JavaScript/Bash脚本运行、超时控制、输出捕获）.
netdata-custom-collector
Use when you need Netdata to collect metrics from something it does not already monitor, such as a custom application, an internal service, the output of a script or CLI tool, or a device. Covers the decision tree from the built-in StatsD server (zero collector code) through writing a collector in any language via the…
bump-dependency
Bumps a Python package dependency across Home Assistant Core integrations, regenerates core requirement files, runs verification tests and prek lint, and prepares a pull request with proper release/compare links.
schema-exploration
Lists tables, describes columns and data types, identifies foreign key relationships, and maps entity relationships in a database. Use when the user asks about database schema, table structure, column types, what tables exist, ERD, foreign keys, or how entities relate.