seeding-playbooks

seeding-playbooks is a skill for Claude Code from buildinternet/releases. It costs 78 tokens per session (3,232 once invoked), scanned A, original, Apache-2.0.

A system for coordinating many agents to write playbooks, which are source-specific instructions for fetching an organisation's releases.

In plain words
What is it for?
Use it to discover organisations, prepare prompts, choose models, dispatch batches of writing work, and verify the resulting playbook notes.
Why use it?
It helps keep release-fetching guidance consistent across many organisations and separates general rules from details about each organisation's sources.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions subagents; positional $N argument; mentions Claude Code.

Part of the registry-maintenance plugin — 8 skills shipped together

Good fit Use it to discover organisations, prepare prompts, choose models, dispatch batches of writing work, and verify the resulting playbook notes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/buildinternet/releases/seeding-playbooks
Install

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.

Any agent
npx skills add buildinternet/releases --skill seeding-playbooks
Clone the repo
git clone --depth 1 https://github.com/buildinternet/releases

Made for: Claude Code.

Or install registry-maintenance, the plugin that ships this one along with the rest of its 8 skills.

Wrote 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.

agentmods badge for seeding-playbooks

README.md
[![agentmods](https://agentmods.dev/badge/skills/buildinternet/releases/seeding-playbooks/github.svg)](https://agentmods.dev/skills/buildinternet/releases/seeding-playbooks)
Your own site
<a href="https://agentmods.dev/skills/buildinternet/releases/seeding-playbooks"><img src="https://agentmods.dev/badge/skills/buildinternet/releases/seeding-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.

agentmods 80×15 button for seeding-playbooks

Your own site · 80×15
<a href="https://agentmods.dev/skills/buildinternet/releases/seeding-playbooks"><img src="https://agentmods.dev/badge/skills/buildinternet/releases/seeding-playbooks.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 78 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,232 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 3 findings, 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 Rogue Agent · line 147
    Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.
    Fix: Prevent the skill from modifying its own code, SKILL.md, or configuration files. Treat skill files as read-only at runtime.
  • medium Prompt Injection · line 83
    Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.
    Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
  • medium Rogue Agent · line 227
    Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
    Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00078 $0.03232
Opus 5 $0.00039 $0.01616
Sonnet 5 $0.00016 $0.00646
Haiku 4.5 $0.00008 $0.00323

Measured 9d ago against content hash 44f8be930596, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

seeding-playbooks 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 9d 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.

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

const orgs = JSON.parse(Bun.spawnSync(['releases', 'admin', 'org', 'list', '--json'], { stderr: 'ignore' }).stdout.toString());
.claude/skills/seeding-playbooks/SKILL.md · 243 lines

How it starts

The opening of the file, as written. The whole thing — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Seeding Playbooks

Coordinate bulk creation or enrichment of playbook agent notes across many orgs using parallel sub-agents.

What a playbook is

A playbook is a per-org skill for fetching that org's releases. Same mental model as the global skills in this corpus (parsing-changelogs, managing-sources, etc.) — but scoped to one organization. It tells a future agent (managed or local) how to pull updates from this org: extraction quirks, naming conventions, which sources are canonical, what to skip, where rollups hide.

Global skills teach general patterns; per-source parseInstructions teach source-specific hints; the playbook is the org-level layer between them. When agents fetch any of an org's sources, they should load that org's playbook into context alongside the global skills — the playbook overrides general rules with specific org behavior.

Write notes as instructions to an LLM, not as human documentation. Imperative voice ("Set version=null", "Parse <h2> as version boundaries"), concrete examples from real data, and only observations that change future fetch behavior.

Currently a local-Claude-Code skill. The dispatch pattern below uses Claude Code's Agent tool — that's what's actually wired up. Managed agents (discovery worker, Haiku worker) can spawn sub-agents in principle, but the harness, prompt scaffolding, and rate-limit accounting for managed sub-agent dispatch in this repo haven't been built yet. If/when that gets wired up, the prompts and dispatch shape in this skill port directly.

When to Use

  • Batch-populating playbooks for orgs that have sources but no notes
  • Re-running the verified workflow on existing playbooks to enrich them with data-grounded observations
  • After a wave of new orgs are onboarded and need initial playbook scaffolding

Step 1: Identify Targets

Find orgs that need playbooks. Run this to check coverage:

bun -e "
const orgs = JSON.parse(Bun.spawnSync(['releases', 'admin', 'org', 'list', '--json'], { stderr: 'ignore' }).stdout.toString());
const active = orgs.filter(o => o.sourceCount > 0).sort((a,b) => b.releaseCount - a.releaseCount);
for (const org of active) {
  const playbook = JSON.parse(Bun.spawnSync(['releases', 'admin', 'playbook', org.slug, '--json'], { stderr: 'ignore' }).stdout.toString());
  const status = playbook.notes?.length > 100 ? 'has notes (' + playbook.notes.length + ' chars)' : 'NEEDS PLAYBOOK';
  console.log(org.slug.padEnd(25) + ' sources=' + String(org.sourceCount).padStart(2) + '  ' + status);
}
" 2>/dev/null

Read the full file on GitHub · 243 lines

Changes

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.

  1. 9d ago First seen · 243 lines · 78 tokens per session scan A 44f8be930596

Subscribe to this mod's changes

seeding-playbooks is a skill published in the GitHub repository buildinternet/releases (6 stars, last pushed 5d ago), licensed Apache-2.0. It adds 78 tokens to every session and 3,232 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

xquik-social-data

Use Xquik for X and Twitter social data workflows through its public API, SDKs, MCP server, webhooks, and installable agent skill.

librefang/librefang-registry · 37 tokens

releases-cli

Use the releases CLI to search, browse, and read the Releases.sh changelog registry from the terminal — the keyless, agent-friendly peer of the Releases MCP. Activate when the user mentions "releases CLI", runs a releases command, asks how to install it, or wants to look up releases, sources, orgs, collections, or…

buildinternet/releases-cli · 86 tokens

releases-mcp

Use when the user asks about recent releases, changelogs, what's new in a library, breaking changes, version updates, or wants to compare products. Activates for questions like "what changed in Next.js 15?", "latest Tailwind releases", "compare Bun vs Deno releases".

buildinternet/releases-cli · 64 tokens

analyzing-releases

Analyze release trends across multiple companies to produce competitive intelligence. Use when asked to compare companies, analyze a market segment, identify industry trends, forecast upcoming releases, or answer questions like "what is X shipping lately" or "how does X compare to Y." Also triggers on requests for…

buildinternet/releases-cli · 75 tokens

graphql-expert

GraphQL expert for schema design, resolvers, subscriptions, and performance optimization.

librefang/librefang-registry · 19 tokens

openapi-expert

OpenAPI/Swagger expert for API specification design, validation, and code generation.

librefang/librefang-registry · 20 tokens