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 majiayu000/spellbook --skill incident-slo-runbookgit clone --depth 1 https://github.com/majiayu000/spellbookWrote 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/majiayu000/spellbook/incident-slo-runbook)<a href="https://agentmods.dev/skills/majiayu000/spellbook/incident-slo-runbook"><img src="https://agentmods.dev/badge/skills/majiayu000/spellbook/incident-slo-runbook/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/majiayu000/spellbook/incident-slo-runbook"><img src="https://agentmods.dev/badge/skills/majiayu000/spellbook/incident-slo-runbook.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.00070 | $0.00402 |
| Opus 5 | $0.00035 | $0.00201 |
| Sonnet 5 | $0.00014 | $0.00080 |
| Haiku 4.5 | $0.00007 | $0.00040 |
Grade A, and why
incident-slo-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 12d 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.
What it actually says
Incident SLO Runbook
Purpose
Use this skill to connect observability to action. Metrics and logs are not enough; each critical user journey needs an SLO, alert, owner, response path, and post-incident learning loop.
SLO Design
Define:
- User journey or system capability.
- SLI: request success, latency, freshness, durability, or job completion.
- SLO target and measurement window.
- Error budget and burn-rate alerts.
- Exclusions with rationale.
- Dashboard and data source.
- Owner and escalation path.
Avoid vanity metrics. Prefer user-visible success and latency over internal counters unless internal counters are the only reliable proxy.
Runbook Requirements
Each runbook should include:
- Symptom and alert name.
- Impacted users or systems.
- First 5-minute checks.
- Triage decision tree.
- Mitigation steps with commands.
- Rollback or failover path.
- Escalation owner.
- Customer/support communication note.
- Postmortem trigger.
Commands must be safe to run or explicitly labeled destructive.
Incident Flow
- Declare severity and incident commander.
- Confirm impact from live evidence.
- Stabilize with the lowest-risk mitigation.
- Communicate status on a fixed cadence.
- Preserve evidence before cleanup.
- Write a blameless postmortem with action items and owners.
Output Shape
service_or_journey:
slo:
alerts:
dashboard_or_queries:
runbook:
escalation:
postmortem_template:
verification:
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.
- 12d ago First seen · 63 lines · 70 tokens per session scan A 78027b49edde
incident-slo-runbook is a skill published in the GitHub repository majiayu000/spellbook (278 stars, last pushed today), licensed MIT. It adds 70 tokens to every session and 402 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-30.
Other skills, from other repositories
pneuma-session
Instructions for renaming an active Pneuma session and replacing its default preview with a useful title and summary. A Pneuma session is one work area inside a larger project.
session-handoff
Use when the user wants to hand off, transfer, pause, or continue the current session in a new session or with another agent — asks for a "session handoff", a "prompt para a próxima sessão", to "continuar de onde paramos", or invokes /session-handoff; also when context is running low and in-flight work must survive a…
Cursor rules for Hashgraph Online development with TypeScript, building AI agent
Cursor rules for Hashgraph Online development with TypeScript, building AI agents on Hedera with RegistryBrokerClient.
Cursor rules for Next
Cursor rules for Next.js development with React and TypeScript integration.
Cursor rules for Next
Cursor rules for Next.js development with TypeScript and Tailwind CSS integration.
Cursor rules for optimization development with Rell Blockchain code integration
Skill "Cursor rules for optimization development with Rell Blockchain code integration" from AmariahAK/atlarix-skills, covering when to use this skill, source, core concepts and modules.