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/fattain-naime/engineering-docs/technical-runbooknpx skills add fattain-naime/engineering-docs --skill technical-runbookgit clone --depth 1 https://github.com/fattain-naime/engineering-docsWhat 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.00062 | $0.03699 |
| Opus 5 | $0.00031 | $0.01850 |
| Sonnet 5 | $0.00012 | $0.00740 |
| Haiku 4.5 | $0.00006 | $0.00370 |
Grade A, and why
technical-runbook scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -vI https://[domain] 2>&1 | grep -i "expire\|issuer\|subject" How it starts
The opening of the file, as written. The whole thing — 254 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Produce a runbook that enables any trained engineer - with no prior knowledge of this specific service - to respond to an alert, diagnose a failure, and execute recovery procedures.
A runbook is not a tutorial or an architecture overview. It is a rapid-reference guide for someone who is paged at 3 AM and needs to resolve an incident in 15 minutes, not learn the system from scratch.
Input
Works best with: The name of the service being documented. Also valuable: The alert definitions, common failure modes, diagnostic commands, architecture overview, and escalation contacts.
Example invocation: Write a runbook for the PayFlow payment gateway. It's a PHP 8.3 app on Nginx/PHP-FPM, MySQL primary + replica, Redis for sessions/cache, and a queue worker process for async jobs. Alerts fire for: high 5xx rate, slow DB queries, queue depth > 1000, and PHP-FPM pool exhaustion.
Key Concepts
What a Good Runbook Contains (Google SRE Standard)
- Overview - What the service does, its SLA, and its dependencies (30 seconds to read)
- Monitoring and Dashboards - Where to look when something is wrong
- Alert Response Procedures - One procedure per alert: diagnosis, mitigation, escalation
- Common Failure Modes - The top 5-10 failures that happen repeatedly
- Diagnostic Commands - The exact commands to run for each symptom
- Escalation Path - Who to call when the runbook cannot resolve the issue
- Maintenance Procedures - Restart, scale, backup, restore
MTTR Reduction
The primary goal of a runbook is to reduce MTTR. Every section should ask: "Can an on-call engineer execute this step in < 5 minutes?" If not, simplify or add more specific commands.
Certificate Management and Rotation
TLS certificates are a common source of outages when they expire or are misconfigured. Document:
- Certificate inventory: Every certificate in use, its issuer, expiry date, and the service(s) it protects.
- Rotation procedure: Exact steps to renew and deploy a new certificate. Include both automated (Let's Encrypt / certbot) and manual (purchased certificate) paths.
- Rotation schedule: How often certificates are rotated (e.g., 90 days for Let's Encrypt, annually for purchased certs). Document the reminder/automation mechanism.
- Emergency rotation: What to do if a certificate is compromised or expires unexpectedly. Include the expedited path (e.g., bypassing normal change control).
- Verification commands: How to verify a certificate is correctly deployed and valid after rotation:
echo | openssl s_client -connect [domain]:443 -servername [domain] 2>/dev/null | openssl x509 -noout -dates curl -vI https://[domain] 2>&1 | grep -i "expire\|issuer\|subject"
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.
- 2d ago First seen · 254 lines · 62 tokens per session scan A 979cac7cefa4
technical-runbook is a skill published in the GitHub repository fattain-naime/engineering-docs (4 stars, last pushed 18d ago), licensed MIT. It adds 62 tokens to every session and 3,699 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…