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 SienkLogic/plan-build-run --skill seedgit clone --depth 1 https://github.com/SienkLogic/plan-build-runWrote 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/sienklogic/plan-build-run/seed)<a href="https://agentmods.dev/skills/sienklogic/plan-build-run/seed"><img src="https://agentmods.dev/badge/skills/sienklogic/plan-build-run/seed/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/sienklogic/plan-build-run/seed"><img src="https://agentmods.dev/badge/skills/sienklogic/plan-build-run/seed.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.00018 | $0.00586 |
| Opus 5.5 | $0.00007 | $0.00234 |
| Sonnet 5.5 | $0.00004 | $0.00117 |
| Haiku 4.5 | $0.00002 | $0.00059 |
Grade A, and why
seed 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 1mo 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
STOP — DO NOT READ THIS FILE. You are already reading it.
/pbr:seed — Plant Ideas for Future Milestones
Capture a forward-looking idea with trigger conditions. Seeds auto-surface during /pbr:new-milestone when trigger conditions match the new milestone's scope.
Seeds beat deferred items because they preserve WHY, define WHEN, and auto-present.
Step 0 — Banner
╔══════════════════════════════════════════════════════════════╗
║ PLAN-BUILD-RUN ► SEED ║
╚══════════════════════════════════════════════════════════════╝
Step 1 — Parse Idea
If $ARGUMENTS is empty, ask: "What's the idea? (one sentence)"
Step 2 — Gather Context
Ask focused questions:
- Trigger: "When should this surface? (e.g., 'when we add user accounts', 'next major version')"
- Why: "Why does this matter? What problem does it solve?"
- Scope: Small (quick task) / Medium (phase or two) / Large (full milestone)
Step 3 — Collect Breadcrumbs
Search codebase for related files. Check STATE.md decisions, ROADMAP.md phases, todos.
Step 4 — Write Seed
mkdir -p .planning/seeds
Find next seed number. Write .planning/seeds/SEED-{NNN}-{slug}.md:
---
id: SEED-{NNN}
status: dormant
planted: {ISO date}
planted_during: {current milestone/phase}
trigger_when: "{trigger}"
scope: "{small|medium|large}"
---
# SEED-{NNN}: {idea}
## Why This Matters
{why}
## When to Surface
**Trigger:** {trigger}
## Breadcrumbs
{related files and references}
Step 5 — Report
Seed planted: SEED-{NNN} — {idea}
Trigger: {trigger}
Integration with /pbr:new-milestone
The new-milestone skill should scan .planning/seeds/ and present matches:
- Read each seed's
trigger_whenfield - Compare against the new milestone's name/scope/goals
- Present matching seeds to the user for inclusion
Anti-Patterns
- DO NOT plant seeds for immediate work — use todos or backlog instead
- DO NOT auto-activate seeds — always present to user during milestone creation
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.
- 1mo ago First seen · 88 lines · 18 tokens per session scan A d9d5b72a9821
seed is a skill published in the GitHub repository SienkLogic/plan-build-run (19 stars, last pushed 6mo ago), licensed MIT. It adds 18 tokens to every session and 586 once invoked, about $0.0001 per session on Opus 5.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-09-03.
Other skills, from other repositories
self-assessment
Interactive skill assessment with personalized learning path generation.
investigate
Systematic root-cause debugging: find the cause before writing any fix.
release-notes-generator
Generate release notes in 3 formats (CHANGELOG.md, PR body, Slack announcement) from git commits. Automatically categorizes changes and converts technical language to user-friendly messaging. Use for releases, changelogs, version notes, what's new summaries, or ship announcements.
sandbox-unblock
Diagnostic protocol to run before reporting a sandbox blocker or asking for a configuration change. Eight checks that eliminate false positives, then a report template the person holding the settings can act on. On one measured day, six of eight reported blockers turned out to be false, all from the same handful of…
talk-stage3-concepts
Builds a numbered, categorized concept catalogue from the talk summary and timeline, scoring each concept HIGH / MEDIUM / LOW for talk potential with optional repo enrichment. Use when you need a structured inventory of concepts before choosing a talk angle, or when assessing which ideas have the strongest…
talk-stage4-position
Generates 3-4 strategic talk angles with strength/weakness analysis, title options, CFP descriptions, and a peer feedback draft, then enforces a mandatory CHECKPOINT for user confirmation before scripting. Use when deciding how to frame a talk, preparing a CFP submission, or choosing between multiple narrative angles.