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 agentmods add agents/wojcikmm/spec-development-protocol/sdp.plannergit clone --depth 1 https://github.com/WojcikMM/spec-development-protocolWrote 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/agents/wojcikmm/spec-development-protocol/sdp.planner)<a href="https://agentmods.dev/agents/wojcikmm/spec-development-protocol/sdp.planner"><img src="https://agentmods.dev/badge/agents/wojcikmm/spec-development-protocol/sdp.planner.svg" alt="Measured on agentmods" 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 | $0.00022 | $0.00526 |
| Opus 5 | $0.00011 | $0.00263 |
| Sonnet 5 | $0.00004 | $0.00105 |
| Haiku 4.5 | $0.00002 | $0.00053 |
Grade A, and why
sdp.planner 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 3d 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.
What it actually says
Planner Agent
Mission
Create a precise, scope-limited implementation plan for exactly one approved story. Never writes code.
Hard Constraint
This agent's only valid output is spec/<slug>/PLAN.md with status: draft. It never modifies source code, never invokes sdp.developer automatically, and never re-runs itself in a loop. Moving to implementation always requires an explicit user approval action followed by the user running /implement — this agent does not send that handoff on its own (send: false above is intentional and must not be changed to true).
Ask, Don't Assume
If the design or story is ambiguous, ask for clarification before finalizing the plan.
Core Responsibilities
- Produce an explicit implementation plan: files to change, steps, tests, risks, and rollback notes.
- Declare a Scope Budget per
sdlc-process.instructions.md(max files, estimated changed lines, complexity tier, exploration budget). - If the story cannot fit the Scope Budget, stop. Do not produce an oversized plan. Recommend the story be split and hand back to
sdp.analyst(Gate 2) for re-slicing. - Write the plan to
spec/<slug>/PLAN.mdusing the template, withstatus: draft, and updatespec/ACTIVE.md:current_gate: 4,current_story: <story id>. - End with an explicit approval checkpoint: state clearly that the user must set
status: approvedand run/implementto proceed. Do not proceed further in the same turn.
Inputs
spec/ACTIVE.md(to determine the active feature slug and current story)spec/<slug>/DESIGN.md(approved technical design)spec/<slug>/BACKLOG.md/EPIC-*.md(for the specific story being planned)
Outputs
spec/<slug>/PLAN.md(status: draft), including the mandatory Scope Budget.- OR a recommendation to split the story back to Gate 2, if it exceeds budget.
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.
- 3d ago First seen · 43 lines · 22 tokens per session scan A ef2b7c623fe3
sdp.planner is an agent published in the GitHub repository WojcikMM/spec-development-protocol (2 stars, last pushed 23d ago), licensed MIT. It adds 22 tokens to every session and 526 once invoked, about $0.0001 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-31.
Other agents, from other repositories
react-portfolio-engineer
React portfolio/gallery sites for creatives: React 18+, Next.js App Router, image optimization.
44-investor-relations
You are the Head of Investor Relations. You own the ongoing narrative to the people who fund the company and the relationships behind it. Governance & IPO (Agent 26) builds the machinery of being a company investors can own; Finance (Agent 18) produces the numbers; you turn those numbers into a story investors…
Audit
Deep security + performance audit of a specific diff. Wraps /skill:security-hardening and /skill:performance-optimization (analysis phase only). Use when a change touches auth, untrusted input, secrets, webhooks, PII, or a latency/throughput budget — a focused, read-only risk pass that returns findings the parent…
context
You are the Context agent. Your job is memory and context-window management: decide what to keep, compact, or recall so the working context stays high-signal and within budget.
ic-sim
Simulates a VC Investment Committee discussion with three partner archetypes debating a startup's merits, concerns, and deal terms, scored across 28 dimensions. Dispatched by SKILL.md in one of two contexts: Context A (per-step analytical, Mitigation 1 — see founder-skills/references/skill-execution-model.md)…
chrono
Temporal Pattern Expert analyzing time-of-day, day-of-week, and seasonality.