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 OutlineDriven/odin-claude-plugin --skill debuggit clone --depth 1 https://github.com/OutlineDriven/odin-claude-pluginWrote 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/outlinedriven/odin-claude-plugin/debug)<a href="https://agentmods.dev/skills/outlinedriven/odin-claude-plugin/debug"><img src="https://agentmods.dev/badge/skills/outlinedriven/odin-claude-plugin/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/outlinedriven/odin-claude-plugin/debug"><img src="https://agentmods.dev/badge/skills/outlinedriven/odin-claude-plugin/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.00033 | $0.02714 |
| Opus 5.5 | $0.00013 | $0.01086 |
| Sonnet 5.5 | $0.00007 | $0.00543 |
| Haiku 4.5 | $0.00003 | $0.00271 |
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.
How it starts
The opening of the file, as written. The whole thing — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
A bug is a falsified assumption. Build a signal that can catch it, then find the smallest assumption that explains the divergence.
When to Apply / NOT
Apply: test fails and cause unclear; production stack trace; intermittent / flaky behavior; wrong output without crash; regression after known commit window; heisenbug.
NOT apply: performance regression with correct outputs; security defect; symptom obvious from one-line read; architectural confusion.
Diagnostic process
Do not skip a phase unless you explicitly justify why. A feedback loop comes before a theory about the code.
Phase 1 — Build a feedback loop
This is the skill. Build a tight pass/fail signal that goes red on this bug before hypothesizing. Bisection, hypotheses, and probes consume that signal; without it, reading code is guesswork. Spend disproportionate effort here. Be creative and do not give up early.
Ways to construct one
Try these in roughly this order:
- Failing test at a seam that reaches the bug: unit, integration, or end-to-end.
- HTTP script against a running development server.
- CLI invocation with fixture input, comparing stdout with a known-good snapshot.
- Headless browser script that drives the UI and asserts on the DOM, console, or network.
- Replay a captured trace by saving a real request, payload, or event log and replaying it through the isolated path.
- Throwaway harness that starts the smallest useful system subset with mocked dependencies and one call through the bug path.
- Property or fuzz loop that runs many generated inputs and detects the failure mode.
- Bisection harness that automates checking a known commit, dataset, or version range so
git bisect runcan use it. - Differential loop that runs the same input through an old and new version, or two configurations, then compares their output.
- Human-in-the-loop shell script only when a person must act. Copy and adapt
scripts/hitl-loop.template.sh; the agent runs it and captured output returns to the investigation.
What ships with it
5 files 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.
- 1mo ago First seen · 167 lines · 33 tokens per session scan A 41c1283db7aa
debug is a skill published in the GitHub repository OutlineDriven/odin-claude-plugin (37 stars, last pushed 21d ago), licensed Apache-2.0. It adds 33 tokens to every session and 2,714 once invoked, about $0.0001 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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…