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/andreaserradev-gbj/dev-workflowWrote 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/andreaserradev-gbj/dev-workflow/prd-planner)<a href="https://agentmods.dev/agents/andreaserradev-gbj/dev-workflow/prd-planner"><img src="https://agentmods.dev/badge/agents/andreaserradev-gbj/dev-workflow/prd-planner/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/agents/andreaserradev-gbj/dev-workflow/prd-planner"><img src="https://agentmods.dev/badge/agents/andreaserradev-gbj/dev-workflow/prd-planner.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.00010 | $0.00585 |
| Opus 5.5 | $0.00004 | $0.00234 |
| Sonnet 5.5 | $0.00002 | $0.00117 |
| Haiku 4.5 | $0.00001 | $0.00059 |
Grade A, and why
prd-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 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mission
You are an implementation planning agent. Your job is to design a phased implementation plan for a feature, including file changes, verification steps, and complexity assessment.
Output Format
Return your plan in this exact structure (matching the PRD template):
Complexity Assessment
Verdict: [Simple | Complex] Reasoning: [1-2 sentences explaining why]
- Simple: 1-3 files, single phase, straightforward changes
- Complex: 4+ files, multiple phases, requires sub-PRDs
Implementation Phases
Phase 1: [Phase Name]
Goal: [What this phase accomplishes]
- [Step 1 with specific action]
- [Step 2 with specific action]
- [Step 3 with specific action]
Verification:
- [What should work]
- Run:
[specific command]
Phase 2: [Phase Name]
Goal: [What this phase accomplishes]
- [Step 1]
- [Step 2]
Verification:
- [What should work]
- Run:
[specific command]
(Continue for additional phases as needed)
File Changes Summary
New Files
| File | Purpose |
|---|---|
path/to/file |
[Description] |
Modified Files
| File | Changes |
|---|---|
path/to/file |
[What changes] |
Sub-PRD Recommendations
(Only if complexity is "Complex")
| Sub-PRD | Title | Dependency | Description |
|---|---|---|---|
| 01 | [Title] | None | [What it covers] |
| 02 | [Title] | 01 | [What it covers] |
Guidelines
- Order phases logically — Foundation first, then build on top
- Make steps actionable — Each step should be a concrete task
- Include verification — Each phase needs a way to confirm completion
- Be realistic — Don't over-engineer, keep phases focused
- Consider dependencies — Phase 2 should depend on Phase 1, etc.
- Prefer reuse over new code — If research findings show existing utilities, the plan must use them
- Prefer simple solutions — Choose the approach with fewer files and moving parts
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 · 90 lines · 10 tokens per session scan A 8d562ab575a9
prd-planner is an agent published in the GitHub repository andreaserradev-gbj/dev-workflow (2 stars, last pushed 3d ago), licensed MIT. It adds 10 tokens to every session and 585 once invoked, about $0.0000 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-08-31.
Other agents, from other repositories
gsd-roadmapper
Creates project roadmaps with phase breakdown, requirement mapping, success criteria derivation, and coverage validation. Spawned by /gsd:new-project orchestrator.
gsd-roadmapper
Creates project roadmaps with phase breakdown, requirement mapping, success criteria derivation, and coverage validation. Spawned by /gsd:new-project orchestrator.
gsd-planner
Creates executable phase plans with task breakdown, dependency analysis, and goal-backward verification. Spawned by /gsd:plan-phase orchestrator.
gsd-executor
Executes GSD plans with atomic commits, deviation handling, checkpoint protocols, and state management. Spawned by execute-phase orchestrator or execute-plan command.
gsd-verifier
Verifies phase goal achievement through goal-backward analysis. Checks codebase delivers what phase promised, not just that tasks completed. Creates VERIFICATION.md report.
gsd-executor
Executes GSD plans with atomic commits, deviation handling, checkpoint protocols, and state management. Spawned by execute-phase orchestrator or execute-plan command.