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 matteotitta/genesys-skills --skill runbookgit clone --depth 1 https://github.com/matteotitta/genesys-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/matteotitta/genesys-skills/runbook)<a href="https://agentmods.dev/skills/matteotitta/genesys-skills/runbook"><img src="https://agentmods.dev/badge/skills/matteotitta/genesys-skills/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/matteotitta/genesys-skills/runbook"><img src="https://agentmods.dev/badge/skills/matteotitta/genesys-skills/runbook.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Agent Snooping · line 89 Skill reads from agent configuration directories (.claude/, .codex/, .gemini/). These directories may contain API keys, personal settings, and other credentials that the skill has no legitimate need to access.Fix: Remove all code or instructions that access agent configuration directories (.claude/, .codex/, .gemini/). If configuration values are needed, pass them explicitly as parameters or environment variabl
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.00119 | $0.01743 |
| Opus 5 | $0.00060 | $0.00872 |
| Sonnet 5 | $0.00024 | $0.00349 |
| Haiku 4.5 | $0.00012 | $0.00174 |
Grade A, and why
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.
How it starts
The opening of the file, as written. The whole thing — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/runbook — Synthesize docs into actionable runbooks
Turn scattered documentation, config files, and tribal knowledge into a structured runbook that anyone can follow. Produces step-by-step procedures with troubleshooting sections, common gotchas, and recovery steps.
Claude Code Triggers
Invoke this skill when user says:
- "/runbook [topic or path]"
- "Create a runbook for..."
- "Document how to..."
- "Write a troubleshooting guide for..."
- "How do I set up...?" (when the answer should be saved as a runbook)
- "Write onboarding docs for..."
Do NOT invoke when:
- User wants a one-off answer (just answer directly)
- User wants a client proposal (use
/client-proposals) - User wants content strategy docs (use
/content-strategy)
Inputs
| Parameter | Required | Description |
|---|---|---|
| Source(s) | Yes | File paths, folder paths, or topic description to synthesize |
| Type | No | setup / troubleshooting / onboarding / workflow / reference (default: inferred) |
| Audience | No | self (personal reference) / client (handoff doc) / team (onboarding guide) (default: self) |
Process
Step 1: Gather sources
Read all provided source documents. If a folder is given, scan for relevant files:
.mdfiles (SKILL.md, CLAUDE.md, README).mjs/.js/.pyfiles (read header comments and docstrings).jsonconfig files (extract structure and key settings).shscripts (extract usage patterns and flags)
If only a topic is given (no paths), search the codebase for relevant files:
Glob for: **/*{topic}*
Grep for: relevant terms in.claude/ and project files
Step 2: Identify runbook type
Based on the sources and user intent, classify the runbook:
- Setup — "How to install/configure/initialize X from scratch"
- Troubleshooting — "When X breaks, here's how to diagnose and fix it"
- Onboarding — "New to X? Here's everything you need to know"
- Workflow — "How to do X step-by-step (recurring process)"
- Reference — "Quick reference card for X (flags, configs, common commands)"
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 · 225 lines · 119 tokens per session scan A 9ee1a880c2c9
runbook is a skill published in the GitHub repository matteotitta/genesys-skills (36 stars, last pushed 1mo ago), licensed MIT. It adds 119 tokens to every session and 1,743 once invoked, about $0.0006 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
gingiris-b2b-growth
🇺🇸 B2B SaaS Growth — PLG vs SLG Playbook — Diagnose whether your problem is distribution, pricing, or PMF. PLG/SLG selection by ACV and sales cycle, the 5-stage path from $0 to $10M ARR, NRR discipline, affiliate & channel motion, enterprise tiering. Built from HeyGen, Deel, Vercel, Supabase, Snowflake patterns.…
gr-b2b-growth
A guide to growing a business-to-business software product from early user research to large-scale sales. B2B software is sold to companies rather than individual consumers.
go-to-market-playbook
A reusable Go-to-Market strategy template for both B2B and B2C launches. Covers positioning, messaging, ICP definition, channel selection, and competitive analysis frameworks. By @WeiYipei.
gingiris-go-global
🇺🇸 AI Product / SaaS Go-Global Complete SOP — From competitor research to launch to monetization. A full-cycle playbook covering Phase 0-5 (market validation, positioning, first 100 users, user interviews, beta-to-growth) plus open-source launch, Product Hunt, Reddit, SEO/GEO, conversion, and org principles.…
gr-competitor-research
Your competitor just launched. You have no idea how they grew so fast. Should you reverse-engineer their website? Track their social media? Map their growth flywheel? This gives you the complete SOP — from Wayback Machine snapshots to X/Twitter propagation analysis to growth flywheel scoring. Built from 150+ AI…
ai-launch-playbook
Launch your AI product to global attention — the playbook behind Manus, Devin, and AFFiNE's breakout launches. Covers AI-specific GTM strategy, hype cycle management, waitlist tactics, and multi-market rollout for maximum day-one impact.