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/atuljha23/holocron/debug-playbooknpx skills add atuljha23/holocron --skill debug-playbookgit clone --depth 1 https://github.com/atuljha23/holocronWrote 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/atuljha23/holocron/debug-playbook)<a href="https://agentmods.dev/skills/atuljha23/holocron/debug-playbook"><img src="https://agentmods.dev/badge/skills/atuljha23/holocron/debug-playbook.svg" alt="Measured on agentmods" 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.00034 | $0.00630 |
| Opus 5 | $0.00017 | $0.00315 |
| Sonnet 5 | $0.00007 | $0.00126 |
| Haiku 4.5 | $0.00003 | $0.00063 |
Grade A, and why
debug-playbook 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 5d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debug playbook
The order of operations matters more than the tools.
1. Reproduce
Nothing else is useful until you can make the bug happen on demand.
- Exact command / action / input that triggers it
- Minimum conditions — strip away anything not required
- If you can't repro, narrow: which environments? which users? which data? which times?
- Unreproducible bugs are intermittent bugs, which are race / env / state leaks — treat them as such.
2. Hypothesize
List 2–3 concrete theories. For each:
- What you think is happening (one sentence)
- What observation would confirm it
- What observation would kill it
If you have only one hypothesis, you're not thinking hard enough — or it's so obvious you should skip to step 4.
3. Probe
Add the cheapest probe that separates your top two hypotheses.
- A targeted log line > reading the code again
git bisectwhen the timeline is wide and the test is binarystrace/dtrace/perfwhen the surface is the runtime, not the code- Differential execution — run on a known-good input and a known-bad input, diff the trace
Resist the urge to add logs everywhere. Add one at the pivot point.
4. Locate
When observation singles out the hypothesis, point at the line. Not the region — the line.
Ask: why does this line break? What invariant did we assume here that isn't true?
5. Fix
Minimum change that resolves the root cause. Nothing adjacent.
- Not: "add a try/catch so we don't see the error"
- Not: "bump the retry so it eventually succeeds"
- Not: "rewrite this section while I'm here"
6. Guard
Add a test that fails without your fix and passes with it. The test should target the condition, not mimic the scenario.
Anti-patterns
- Shotgun debugging — changing five things, one passed. Revert four of them and find which one.
- Bandaid reflex — catching exceptions you don't understand. You're hiding the bug, not fixing it.
- Upgrade cure — "upgrading the dep fixed it". Maybe. Or maybe it re-broke differently. Read the changelog.
- "Works on my machine" — an environment bug. Find the environmental difference.
- Adding retries — every retry hides a bug you didn't diagnose.
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.
- 5d ago First seen · 79 lines · 34 tokens per session scan A 980722cbb694
debug-playbook is a skill published in the GitHub repository atuljha23/holocron (2 stars, last pushed 4mo ago), licensed MIT. It adds 34 tokens to every session and 630 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
survey-generator
Compile a structured literature survey on any AI/ML topic. Agent curates a research bundle (taxonomy + sections + bibliography of real papers) from a public anchor resource, then a chosen LLM generates the survey artifact. Output target is a wiki page (markdown), not a one-off HTML — survey lands in /derived/surveys/…
batch-orchestration
Decompose large-scale changes into independent units and spawn parallel agents in isolated worktrees. Use for migrations, refactors, codemods, and any change touching 10+ files with the same pattern.
design-engineering
Apply interface craft when building or reviewing UI - motion, easing, timing, springs, component feel, and visual foundations. Use when building a component, animation, transition, hover or press state, modal, drawer, toast, or when polishing an interface so it feels right. Says "make this feel better", "add an…
skill-optimizer
SkillOpt-flavored offline training loop for any SKILL.md. Treats accumulated learn-rule corrections as training trajectories, proposes bounded patches via an optimizer LLM, gates each candidate against a held-out validation set built from the user's own past corrections, and ships only candidates that demonstrably…
skill-router
The index of every pro-workflow skill and command, grouped by job, with when to reach for each and whether it is human-run or auto-triggered. Use when you are not sure which skill fits, want the full map, or ask "what can this do", "which skill for X", "list the workflow".
sprint-status
Track parallel work sessions and prevent confusion across multiple Claude Code instances. Every major step ends with a status line. Every question re-states project, branch, and task.