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 samuelgudi/iknowkungfu --skill deployment-runbookgit clone --depth 1 https://github.com/samuelgudi/iknowkungfuWrote 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/samuelgudi/iknowkungfu/deployment-runbook)<a href="https://agentmods.dev/skills/samuelgudi/iknowkungfu/deployment-runbook"><img src="https://agentmods.dev/badge/skills/samuelgudi/iknowkungfu/deployment-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/samuelgudi/iknowkungfu/deployment-runbook"><img src="https://agentmods.dev/badge/skills/samuelgudi/iknowkungfu/deployment-runbook.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.00058 | $0.01185 |
| Opus 5 | $0.00029 | $0.00593 |
| Sonnet 5 | $0.00012 | $0.00237 |
| Haiku 4.5 | $0.00006 | $0.00119 |
Grade A, and why
deployment-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 11d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
deployment-runbook
A deployment runbook is a procedure someone can follow to ship a service safely without already knowing how it works. The test of a good runbook: hand it to a person who has never deployed this service, and they succeed — or fail safely and recover — without asking anyone.
Deploys go wrong precisely when the conditions are worst: late, under pressure, done by whoever is available. A runbook is the artifact that makes the procedure independent of who is running it and how stressed they are.
Use this skill when
- A service is deployed by hand, or by a procedure that lives only in one person's head.
- An existing runbook exists but people still have to ask questions to use it.
- You are setting up a new service and want the deploy procedure written down before the first 2am incident.
Structure
A runbook has six sections, in this order:
- Prerequisites — what must be true before you start: access and credentials needed, tools that must be installed, the branch/artifact/version being deployed. If a prerequisite is missing, the operator finds out here, not three steps in.
- Pre-flight checks — quick checks that this is a safe moment to deploy: is the target healthy now, is there a freeze in effect, is the change actually the one intended. Each check has a clear pass/fail.
- Deploy steps — the numbered procedure. See the rule below.
- Verification — how to know the deploy worked. Objective, not "looks fine".
- Rollback — how to undo it. See the rule below.
- Post-deploy — anything to do after success: announce, close the ticket, re-enable something that was paused, watch a dashboard for N minutes.
The rule for deploy steps
Every step is three things: the exact command, the expected result, and what to do if it does not happen.
3. Apply the database migration:
`./manage.py migrate`
Expected: ends with "Applying <name>... OK", exit code 0.
If it fails: do NOT proceed to step 4. The schema is now partially
applied — go to Rollback step R2 before retrying.
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.
- 11d ago First seen · 72 lines · 58 tokens per session scan A 75c7fb80682d
deployment-runbook is a skill published in the GitHub repository samuelgudi/iknowkungfu (2 stars, last pushed 1mo ago), licensed MIT. It adds 58 tokens to every session and 1,185 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…