Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Abilityai/abilitiesnpx agentmods add skills/abilityai/abilities/create-playbookWrote 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/abilityai/abilities/create-playbook)<a href="https://agentmods.dev/skills/abilityai/abilities/create-playbook"><img src="https://agentmods.dev/badge/skills/abilityai/abilities/create-playbook/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/abilityai/abilities/create-playbook"><img src="https://agentmods.dev/badge/skills/abilityai/abilities/create-playbook.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.00025 | $0.11394 |
| Opus 5.5 | $0.00010 | $0.04558 |
| Sonnet 5.5 | $0.00005 | $0.02279 |
| Haiku 4.5 | $0.00003 | $0.01139 |
Grade B, and why
create-playbook scanned grade B 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.
Enumerates other installed skillsmediumAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
ls -d .claude/skills/*/ 2>/dev/null | head -10 How it starts
The opening of the file, as written. The whole thing — 504 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Playbook
ℹ️ First, set expectations: before anything else, print one short line with this skill's version and its most recent change — the top entry of
metadata.changelogabove — e.g.create-playbook vX.Y — recent: <summary>. Then proceed.
Create a new skill. Determines the right complexity tier and generates from the appropriate template.
For concepts and patterns, see the README. Tier templates are bundled with this skill in templates/ — reference them at runtime via
${CLAUDE_SKILL_DIR}/templates/.
Workflow
Step 1: Check for Existing Skills
ls -d .claude/skills/*/ 2>/dev/null | head -10
ls -d ~/.claude/skills/*/ 2>/dev/null | head -10
If similar skill exists, ask: update it, create variant, or proceed with new?
Step 2: Gather Core Requirements
Ask or extract from context:
- Name: lowercase-with-hyphens, descriptive. For project/personal skills the directory name is the command (
name:is display-only); for plugin skillsname:sets the command segment — keep name and directory identical so they never drift. - Purpose → the
description:field: third person, what it does + when to use it, key use case first — the skill listing truncatesdescription+when_to_useat 1,536 characters. - Tools needed: Which tools will it use?
Step 3: Determine Complexity Tier
Ask these questions to classify:
Q1: Does this skill read or write any files, APIs, or external state?
- NO → Tier 1: Simple Skill (skip to Step 4)
- YES → Continue to Q2
Q2: Will this run unattended, on a schedule, or need reliability guarantees?
- NO → Tier 2: Stateful Skill (skip to Step 4)
- YES → Continue to Q3
Q3: What automation level?
- Safe to run completely unattended, no approval needed at any point →
autonomous - Needs human approval at checkpoints →
gated - Human monitors entire execution →
manual
⚠️ Critical: If user says "autonomous" but also mentions approval/review steps, clarify:
"Autonomous playbooks cannot have approval gates — they run unattended and would hang waiting for approval that never comes. Should this be
gatedinstead?"
What ships with it
5 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 Changed · +1 lines 4ccdeaee9b0e
- 7d ago Changed · +1 lines 2ae3d2cd4c5e
- 16d ago Changed · +53 lines 88e1fff8edae
- 1mo ago Changed · +1 lines e256bce9cf71
- 1mo ago First seen · 448 lines · 25 tokens per session scan B 062c180fc8e9
create-playbook is a skill published in the GitHub repository Abilityai/abilities (12 stars, last pushed 3d ago), licensed MIT. It adds 25 tokens to every session and 11,394 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 1 finding (enumerates other installed skills). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…