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 rjmurillo/ai-agents --skill ai-agents-debugging-playbookgit clone --depth 1 https://github.com/rjmurillo/ai-agentsWrote 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/rjmurillo/ai-agents/ai-agents-debugging-playbook)<a href="https://agentmods.dev/skills/rjmurillo/ai-agents/ai-agents-debugging-playbook"><img src="https://agentmods.dev/badge/skills/rjmurillo/ai-agents/ai-agents-debugging-playbook/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/rjmurillo/ai-agents/ai-agents-debugging-playbook"><img src="https://agentmods.dev/badge/skills/rjmurillo/ai-agents/ai-agents-debugging-playbook.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.00124 | $0.06234 |
| Opus 5.5 | $0.00050 | $0.02494 |
| Sonnet 5.5 | $0.00025 | $0.01247 |
| Haiku 4.5 | $0.00012 | $0.00623 |
Grade A, and why
ai-agents-debugging-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 today.
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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ai-agents Debugging Playbook
Symptom-first triage for this repository's known failure modes. Every row below was earned by a real incident; the retro path is cited so you can read the full story. The playbook answers one question: given this symptom, what is the FIRST command to run, what experiment discriminates between causes, and what trap has already cost someone real time here?
Vocabulary used once: a "guard" is a PreToolUse or pre-push hook that can block an action (exit 2 blocks, exit 0 allows). A "drift gate" is a CI check that fails when a generated tree no longer matches its canonical source. A "discriminating experiment" is one cheap action whose outcome splits the hypothesis space in two.
Triggers
triage this failurewhy is my push blockeddebug this CI redwhat does this gate failure meanhook blocked my tool call
When NOT To Use This Skill
| You want | Use instead |
|---|---|
| The full history of an incident (root cause, evidence, what changed) | ai-agents-failure-archaeology |
| To measure something (budgets, telemetry, drift as a number) | ai-agents-diagnostics-toolkit |
| Evidence standards, test layout, how to write the missing test | ai-agents-validation-and-qa |
| The catalog of every env var, marker, and escape hatch | ai-agents-config-catalog |
| How the harness itself behaves (payload shapes, plugin roots) | agent-harness-reference |
| Fix a NON_COMPLIANT session log | Hand-edit against .agents/schemas/session-log.schema.json, re-run scripts/validate_session_json.py |
| Resolve merge conflicts | Agent: merge-resolver |
| Query agent JSONL event logs | observability |
What ships with it
1 file 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.
- today Changed 194fc56abbf0
- 4d ago Changed · +1 lines 6dd99e21909b
- 15d ago Changed 5893e503ef0d
- 16d ago Changed a6cebc38d95d
- 17d ago Changed · +12 lines efe12c9b8461
- 20d ago Changed · +6 lines ea2ef7a74880
- 22d ago Changed 037aff4620c9
- 1mo ago Changed · +2 lines ed449e48a2c7
- 1mo ago Changed 7a0677a9fbdf
- 1mo ago First seen · 152 lines · 124 tokens per session scan A 6a89af761d6f
ai-agents-debugging-playbook is a skill published in the GitHub repository rjmurillo/ai-agents (48 stars, last pushed today), licensed MIT. It adds 124 tokens to every session and 6,234 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
extension-audit-methodology
Systematic 5-dimension audit framework for VS Code extensions — debug hygiene, dead code, performance, menu validation, dependency cleanup.
mcore-create-issue
Investigate a failing GitHub Actions run or job and create a GitHub issue for the failure.
ci-triage
Classify CI failures — distinguish clear regressions from infra flakes and security-test failures. Produces structured failure reports.
ase-code-lint
Lint source code for potential code quality problems. Use when the user wants to "lint" or "check" source code.
gh-fix-ci
Use when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions; use gh to inspect checks and logs, summarize failure context, draft a fix plan, and implement only after explicit approval. Treat external providers (for example Buildkite) as out of scope and report only the details URL.
gitlab-pipeline-debugger
Debug and monitor GitLab CI/CD pipelines for merge requests. Check pipeline status, view job logs, and troubleshoot CI failures. Use this when the user needs to investigate GitLab CI pipeline issues, check job statuses, or view specific job logs.