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/codebygarv/ai-skills/runbook-generatornpx skills add codebygarv/Ai-skills --skill runbook-generatorgit clone --depth 1 https://github.com/codebygarv/Ai-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/codebygarv/ai-skills/runbook-generator)<a href="https://agentmods.dev/skills/codebygarv/ai-skills/runbook-generator"><img src="https://agentmods.dev/badge/skills/codebygarv/ai-skills/runbook-generator.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.00026 | $0.00337 |
| Opus 5 | $0.00013 | $0.00169 |
| Sonnet 5 | $0.00005 | $0.00067 |
| Haiku 4.5 | $0.00003 | $0.00034 |
Grade A, and why
runbook-generator 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 6d 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.
- **Diagnostic Commands**: Copy-pasteable CLI commands (kubectl, curl, SQL) with expected output. What it actually says
Purpose
Produce clear, foolproof, executable operational runbooks for on-call engineers to diagnose, mitigate, and resolve production alerts under pressure.
When to Use
- Creating runbooks for new microservices, alerts, or cron jobs.
- Standardizing incident response procedures across engineering teams.
- Documenting disaster recovery failovers, certificate renewals, and manual database rollbacks.
What to Analyze
- Alert Definition: Alert name, firing trigger threshold, severity, and impacted customer services.
- Triage & Diagnosis: Step-by-step commands and dashboard links to verify if it is a real issue or false positive.
- Mitigation Steps: Fast containment actions (rollback, traffic reroute, scaling up, cache purge).
- Root Cause Resolution: Permanent investigative steps to fix the underlying problem.
- Escalation Policy: Who to page if mitigation does not restore service within 15 minutes.
Output Format
- Alert Metadata: Severity, SLI/SLA impacted, PagerDuty link.
- Diagnostic Commands: Copy-pasteable CLI commands (kubectl, curl, SQL) with expected output.
- Mitigation Playbook: Numbered actions in order of speed.
- Rollback & Safety Checks: How to verify recovery before closing the incident.
Avoid
- Vague instructions like "check the logs" without exact log query filters or links.
- Omitting escalation contacts and secondary on-call details.
What ships with it
2 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.
- 6d ago First seen · 35 lines · 26 tokens per session scan A d541ccd17b71
runbook-generator is a skill published in the GitHub repository codebygarv/Ai-skills (25 stars, last pushed 16d ago), licensed MIT. It adds 26 tokens to every session and 337 once invoked, about $0.0001 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-30.
Other skills, from other repositories
bun-api
Bun runtime API reference for TypeScript scripts. Covers Bun.serve() HTTP/HTTP/2 server with routes and WebSockets, fetch() transport options, Bun.file(), Bun.write(), Bun.$() shell, Bun.spawn(), Bun.Glob, Bun.env, bun:sqlite, Bun.sql() for PostgreSQL/MySQL via DATABASEURL, Bun.s3 for S3-compatible storage, Bun.redis…
deps-upgrade
Validate JavaScript/TypeScript dependency upgrades after an interactive or manual update. Establish the real delta from git, detect peer/engine/type conflicts, extract breaking changes, migrations and adoptable features from release notes, assess held-back or seemingly unused packages, and run verification gates.…
git-pr
PR and MR workflows for GitHub (gh) and GitLab (glab). Creation, review comment handling, thread resolution, review state queries, merging, cost-aware bot review rounds (GitHub: Copilot, CodeRabbit), and Copilot code review configuration (rulesets, custom instructions, billing). Use when creating PRs/MRs, addressing…
git-project
GitHub Projects (v2) setup and management via gh CLI + GraphQL: organize a repo's issues into epics with native sub-issues, drive a board Status flow (Todo -> In Progress -> Done), set Project Priority, classify with native issue Types (Task/Bug/Feature) instead of labels, scope work with milestones (incl. resolving…
git-ci
CI/CD status queries for GitHub Actions (gh) and GitLab CI (glab). Check pipeline status, failing jobs, workflow runs, job logs, and merge readiness. Use when checking CI status, debugging build failures, viewing job logs, watching pipeline progress, or configuring gh/glab CI read-only allowlists. Not for PR workflows…
git-commit
Conventional Commits format for git commits and PR/MR titles. Type prefixes, scope rules, breaking change syntax, and commit message structure. Use when committing changes, writing commit messages, creating PR/MR titles, or formatting squash merge messages. Not for PR workflows (git-pr), CI/CD status (git-ci), or git…