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/ardurai/ardur-agent/write-runbooknpx skills add ArdurAI/ardur-agent --skill write-runbookgit clone --depth 1 https://github.com/ArdurAI/ardur-agentWrote 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/ardurai/ardur-agent/write-runbook)<a href="https://agentmods.dev/skills/ardurai/ardur-agent/write-runbook"><img src="https://agentmods.dev/badge/skills/ardurai/ardur-agent/write-runbook.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.00020 | $0.01143 |
| Opus 5 | $0.00010 | $0.00571 |
| Sonnet 5 | $0.00004 | $0.00229 |
| Haiku 4.5 | $0.00002 | $0.00114 |
Grade A, and why
write-runbook 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing a runbook
A runbook turns a once-solved problem into a procedure anyone on-call can execute at 3am, half-asleep, without your context. Write it for that reader: not the expert who already knows the system, but the tired engineer who has never seen this failure before.
The test of a good runbook is simple — could someone who has never touched this service resolve the incident by following it literally? If a step requires judgement you have not written down, the runbook is not done.
When to write one
Write a runbook when a problem is recurring or likely to recur, has a known response, and is time-sensitive when it happens. A one-off that will never repeat does not need a runbook; it needs a postmortem. A problem with no known response does not need a runbook yet; it needs investigation.
Structure
Follow this order. It matches the order an on-call engineer actually needs the
information. The full skeleton with prompts is in @./template.md.
1. Symptom — how you know you are here
What does the operator observe? Be concrete and matchable:
- The exact alert name or alert text that fires.
- The dashboard panel that goes red and its threshold.
- The user-visible behavior ("checkout returns 503", "search latency > 2s").
The operator arrives holding a symptom, not a diagnosis. They must be able to match what they see against your symptom line in seconds. If two failures look identical at the symptom level, say so and point to the disambiguating check.
2. Impact — how bad, how urgent
- Who is affected and how many (all users, one region, one tenant)?
- What is degraded versus fully down?
- Is there data loss risk, or only availability?
This sets the operator's urgency and tells them whether to page for help before proceeding.
3. Diagnosis — confirm before you act
Steps to confirm this is the failure the runbook addresses, and not a look-alike. Each step is a concrete command or query with the expected output:
# Is the queue actually backed up, or is the metric stale?
$ redis-cli -h <host> LLEN jobs:pending
# Expected when healthy: < 100. If > 10000, this runbook applies.
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.
- 5d ago First seen · 121 lines · 20 tokens per session scan A 21cc6cb95d4d
write-runbook is a skill published in the GitHub repository ArdurAI/ardur-agent (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 20 tokens to every session and 1,143 once invoked, about $0.0001 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
agent-communication-protocol
Open protocol for AI agent interoperability enabling standardized communication between agents, applications, and humans across different frameworks.
analyze-agent-codebase
当用户希望依据源码、配置、schema 和测试，分析 Coding Agent、Agent 框架或多 Agent 系统的真实架构、执行流程、上下文、记忆、工具、权限或扩展点时使用。继续回答同一分析中的定向机制问题或整理专题文档时也使用。普通代码评审、实现或修复任务，以及不需要仓库证据的概念问答不使用。.
worktree
当用户明确要求使用 Git worktree，或需要为一项独立开发工作创建、查找、复用、交接或清理隔离工作目录时使用。普通只读任务、非 Git 仓库，以及当前工作无需独立分支或工作目录时不使用。.
member-studio
当用户希望创建新的 Rovai 队员，或继续调整、确认本次创建中尚未写入的队员名牌和头像方案时使用。普通成员资料咨询、编辑已创建队员，以及只设计角色或头像但不加入名册的任务不使用。.
campfire
当用户希望 Camp 中多位成员共同讨论、从不同角度分析、比较方案、评估利弊或讨论后形成建议时使用。主持人发起和继续整理讨论，成员在收到本次讨论任务时也使用。普通单人问题、无关发言、迟到补充和已经结束的讨论不使用。.
Read-only review
Review the selected implementation and report correctness, security, and maintainability findings. Do not modify workspace files.