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.
git clone --depth 1 https://github.com/melodic-software/claude-code-pluginsWrote 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/plugins/melodic-software/claude-code-plugins/playbooks)<a href="https://agentmods.dev/plugins/melodic-software/claude-code-plugins/playbooks"><img src="https://agentmods.dev/badge/plugins/melodic-software/claude-code-plugins/playbooks/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/plugins/melodic-software/claude-code-plugins/playbooks"><img src="https://agentmods.dev/badge/plugins/melodic-software/claude-code-plugins/playbooks.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
playbooks 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 today.
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
{
"$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
"name": "playbooks",
"version": "0.9.10",
"description": "Doctrine and knowledge playbooks as on-demand skills, plus a maintainer-facing update skill. boris — Boris Cherny's Claude Code workflow tips (howborisusesclaudecode.com); skill-authoring — Anthropic's internal skill-authoring playbook; fable-5 — Claude Fable 5's operating doctrine (self-authored, no upstream). The boris and skill-authoring packs vendor a verbatim upstream baseline; /playbooks:update drift-checks and syncs those baselines centrally (maintainers).",
"author": {
"name": "Melodic Software",
"email": "[email protected]"
},
"license": "MIT",
"keywords": [
"playbooks",
"knowledge",
"doctrine",
"claude-code",
"workflow",
"skill-authoring",
"boris-cherny",
"fable-5",
"best-practices",
"tips"
]
}
What it installs
The manifest is a name and a version. 3 skills travel with it, and installing the plugin installs all of them — 444 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- today Changed cf3ace6a6375
- 2d ago Changed 7f82087ef5c4
- 5d ago Changed 5ab39560abac
- 7d ago First seen · 24 lines scan A 34b1ea126132
playbooks is a plugin published in the GitHub repository melodic-software/claude-code-plugins (16 stars, last pushed today), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-09-03.
Other plugins, from other repositories
collaborative-planning
Collaborative planning commands with iterative requirements gathering. Ensures thorough understanding before implementation through structured Q&A sessions.
local-llm
Manage local Ollama LLM models for development and testing.
parallel-workflows
Parallel workflow orchestration using git worktrees for concurrent Claude Code sessions.
deep-research
Iterative deep research with progressive exploration and structured synthesis.
error-therapist
Audit and rewrite error messages to be helpful and actionable.
content
Content creation and publishing: three writer+optimiser pairs (guides, features, documentation) with research-first workflows, per-content reports, and deterministic audit scoring. Feature writer+optimiser now enforce Technical-Marketing Synthesis (Rule 6: ten sub-checks including coined terminology, dropdown…