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 The-AI-Directory-Company/agents-and-skills --skill runbook-writinggit clone --depth 1 https://github.com/The-AI-Directory-Company/agents-and-skillsWrote 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/the-ai-directory-company/agents-and-skills/runbook-writing)<a href="https://agentmods.dev/skills/the-ai-directory-company/agents-and-skills/runbook-writing"><img src="https://agentmods.dev/badge/skills/the-ai-directory-company/agents-and-skills/runbook-writing/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/the-ai-directory-company/agents-and-skills/runbook-writing"><img src="https://agentmods.dev/badge/skills/the-ai-directory-company/agents-and-skills/runbook-writing.svg" alt="Reviewed on agentmods" width="80" 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.00038 | $0.01241 |
| Opus 5 | $0.00019 | $0.00620 |
| Sonnet 5 | $0.00008 | $0.00248 |
| Haiku 4.5 | $0.00004 | $0.00124 |
Grade A, and why
runbook-writing 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 9d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Runbook Writing
Before you start
Gather the following from the user:
- What system or service does this cover? (Service name, what it does, where it runs)
- What scenario triggers this runbook? (Alert name, error condition, user-reported symptom)
- Who is the intended audience? (On-call generalist, team-specific engineer, external vendor)
- What access or permissions are required? (SSH keys, cloud console roles, VPN, database credentials)
- What is the blast radius if the procedure goes wrong? (Data loss risk, downtime scope, affected users)
If the user says "just write a runbook for the payments service," push back: "Which failure mode? A runbook covers one specific scenario — database connection exhaustion is a different runbook than payment gateway timeouts."
Runbook template
Use the following structure for every runbook:
Purpose
One to two sentences stating what this runbook fixes and when to use it. Include the alert name or trigger condition verbatim so engineers can grep for it. Add a "last verified" date.
Prerequisites
List every tool, permission, and access requirement. The on-call engineer should read this list and immediately know if they can execute the runbook or need to escalate. Example items: cloud console role, SSH/VPN access, specific dashboard URLs, PagerDuty escalation policy membership.
Symptoms and Triggers
Describe observable signals — alert text, log patterns (exact searchable strings), dashboard anomalies, and user-reported behavior.
Step-by-Step Procedure
Number every step. Each step must include:
- The exact command or UI action (copy-pasteable)
- Expected output so the engineer can confirm the step worked
- What to do if the output differs
Use decision branches with explicit if/then routing:
3. Check pg_stat_activity for connection state:
$ psql -h <DB_HOST> -U readonly -c "SELECT state, count(*)
FROM pg_stat_activity WHERE datname = 'checkout' GROUP BY state;"
- IF active queries > 40: proceed to step 4 (kill long-running queries).
- IF idle connections > 40: skip to step 5 (restart service).
- IF neither: escalate — the connection pool issue is not database-side.
What ships with it
3 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.
- 9d ago First seen · 105 lines · 38 tokens per session scan A 438128e78f34
runbook-writing is a skill published in the GitHub repository The-AI-Directory-Company/agents-and-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 38 tokens to every session and 1,241 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-09-03.
Other skills, from other repositories
writing-workflow-skills
Use when adding a new workflow skill to pi-thinkrail-workflow, changing an existing workflow skill's role, trigger, handoff, or structure, or checking a workflow skill against the workflow system's rules. Not for authoring general-purpose skills outside this package.
case-interview-practice
Interactive consulting case interview practice with structured frameworks, feedback mechanisms, and progressive difficulty. Use when preparing for management consulting interviews, case competitions, or business problem-solving exercises.
i18n-localization
Internationalization and localization for global applications. Use when adding multi-language support, handling regional formats, or preparing apps for global markets.
electron-desktop
Desktop application development with Electron for Windows, macOS, and Linux. Use when building cross-platform desktop apps, implementing native OS features, or packaging web apps for desktop.
finance
Financial analysis expertise for financial modeling (DCF, LBO, M&A), valuation, financial statement analysis, capital allocation, treasury management, and corporate finance decisions. Use when building financial models, analyzing statements, or making investment decisions.
investment-memo-generator
Investment memo creation combining financial analysis, document generation, and structured templates. Use when creating investment memos, pitch decks, deal summaries, or investment committee materials.