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/bricerising/enterprise-software-playbook/debugnpx skills add bricerising/enterprise-software-playbook --skill debuggit clone --depth 1 https://github.com/bricerising/enterprise-software-playbookWrote 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/bricerising/enterprise-software-playbook/debug)<a href="https://agentmods.dev/skills/bricerising/enterprise-software-playbook/debug"><img src="https://agentmods.dev/badge/skills/bricerising/enterprise-software-playbook/debug.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 | $0.00069 | $0.01697 |
| Opus 5 | $0.00034 | $0.00848 |
| Sonnet 5 | $0.00014 | $0.00339 |
| Haiku 4.5 | $0.00007 | $0.00170 |
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 4d 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debug (Log → Trace → Metrics)
Overview
This skill is for debugging with existing telemetry. It does not focus on adding instrumentation (use observability when telemetry gaps block triage).
Goal: turn “something is broken/slow” into:
- a concrete symptom + impact statement,
- an evidence-backed hypothesis (or a small set of competing ones),
- a mitigation (rollback/flag/scale) when needed,
- a short list of fix + follow-up tasks.
Inputs / Outputs
Inputs: Symptom description (what's failing/slow); access to logs, traces, and metrics; environment and time window.
Outputs: Root cause diagnosis with evidence, mitigation action, fix plan, learning capture. Feeds follow-ups to observability, resilience, platform, or architecture.
Workflow
0) Establish ground truth (2–5 minutes)
Capture:
- Environment (
local/dev/staging/prod) and time window (start/end). - Symptom (what’s failing/slow) and impact (SLO/user-visible blast radius).
- One exemplar: request/trace ID, job run ID, message ID, or timestamped log line.
1) Logs (find the exemplar and its correlation IDs)
- Find the first error/timeout log line closest to the symptom window.
- Identify correlation keys (prefer stable IDs):
traceId,requestId,spanIdop(route template / RPC method / job name / message type)- error code/type (typed error envelope, gRPC status, HTTP status)
- Pull the full log story for the exemplar (start → downstream call(s) → failure).
Copy/paste helpers live in references/commands.md.
2) Trace (turn the exemplar into a dependency hypothesis)
If you have a traceId, use it.
- Open the trace and confirm the root span matches the suspected operation (
op). - Identify:
- the slowest span(s),
- the first error span(s),
- retries (multiple similar child spans),
- deadline/time budget signals (deadline exceeded, timeout errors).
- Convert that to a dependency statement:
- “
service Ais timing out callingservice BmethodX” - “DB query
Yis slow / missing index / deadlocked” - “Queue consumer is failing on message type
T(poison message)”
- “
What ships with it
2 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.
- 4d ago First seen · 146 lines · 69 tokens per session scan A 3b70bf850fe6
debug is a skill published in the GitHub repository bricerising/enterprise-software-playbook (7 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 69 tokens to every session and 1,697 once invoked, about $0.0003 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
html-ppt-knowledge-arch-blueprint
OpenDesign's incident retro: the daemon-restart data bug, the root cause, the fix, and the systemic follow-ups. Built as a decision-grade product management deck for engineering, SRE, leadership.
release
Guide through the Cortex TMS release process — version bump, changelog, sync, tag, publish. Every step requires user approval.
html-ppt-graphify-dark-graph
OpenDesign's feature business case for the plugin marketplace: the user pain, options, tradeoffs, and the measure of success. Built as a decision-grade product management deck for PM, eng, design, leadership.
frontmcp-guides
Tutorials, end-to-end walkthroughs, and complete reference projects for FrontMCP. Use when you want a getting-started guide, a full worked example, or to learn best practices by following a step-by-step build rather than a single API reference. Includes a beginner weather-API server (tool plus static resource, Zod…
execution
M-1.4 execution skill — 跑 single task 产 patch + 提交 envelope。.
review
M-1.5 review skill — 在 patch 跟 contract 之间找 finding，produce Finding 一等对象。.