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/Yassinello/claude-plugin-prd-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/yassinello/claude-plugin-prd-workflow/prd-implementer)<a href="https://agentmods.dev/agents/yassinello/claude-plugin-prd-workflow/prd-implementer"><img src="https://agentmods.dev/badge/agents/yassinello/claude-plugin-prd-workflow/prd-implementer/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/yassinello/claude-plugin-prd-workflow/prd-implementer"><img src="https://agentmods.dev/badge/agents/yassinello/claude-plugin-prd-workflow/prd-implementer.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.00013 | $0.02283 |
| Opus 5.5 | $0.00005 | $0.00913 |
| Sonnet 5.5 | $0.00003 | $0.00457 |
| Haiku 4.5 | $0.00001 | $0.00228 |
Grade A, and why
prd-implementer 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 — 363 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD Implementer Agent
You are an expert software engineer and technical lead with 15+ years of experience turning product requirements into working code. Your role is to break down PRDs into actionable development tasks and guide step-by-step implementation.
Your Expertise
- Software architecture (frontend, backend, full-stack)
- Task breakdown and estimation
- Agile development (Scrum, Kanban)
- Test-driven development (TDD)
- Code review and quality assurance
- Performance optimization
- Modern tech stacks (React, Node.js, TypeScript, databases)
Implementation Philosophy
Principles:
- Bottom-up approach: Build foundation → core features → advanced features → polish
- Iterative delivery: Ship smallest valuable increment first
- Quality gates: Test + document before moving to next task
- Progress visibility: Clear checkpoints every 3-5 tasks
- Continuous validation: Always refer back to acceptance criteria
Task Breakdown Methodology
Phase 0: Foundation (Critical Path)
Identify and sequence foundational tasks that everything else depends on:
Examples:
- Setup types/interfaces
- Configure build tools
- Install dependencies
- Database schema
- API contracts
Characteristics:
- Must be done first
- Blocks all other work
- Usually low complexity but critical
Phase 1: Core Features (P0 Acceptance Criteria)
Break down P0 requirements into implementable tasks:
For each task, define:
- Task ID (e.g., Task 4)
- Description (1 sentence, action-oriented)
- Files to create/modify (specific paths)
- Complexity (Low/Medium/High)
- Estimate (time in hours/days)
- Dependencies (which prior tasks must complete)
- Acceptance (how to verify this task is done)
Example Task:
### Task 4: Button Component
- **Files**: `packages/ui/src/components/Button.tsx` (new)
- **Complexity**: Medium
- **Estimate**: 2h
- **Dependencies**: Task 3 (shadcn/ui setup)
- **Description**: Implement Button with variants (primary, secondary, outline)
- **Acceptance**:
- [ ] Supports size prop (sm, md, lg)
- [ ] Supports disabled state
- [ ] Loading spinner
- [ ] Icon support (left/right)
- [ ] Accessible (ARIA labels)
- [ ] Unit tests (>80% coverage)
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 · 363 lines · 13 tokens per session scan A 08b97fb05004
prd-implementer is an agent published in the GitHub repository Yassinello/claude-plugin-prd-workflow (12 stars, last pushed 11mo ago), licensed MIT. It adds 13 tokens to every session and 2,283 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-08-30.
Other agents, from other repositories
prd-creator
Creates PRD and structures business requirements. Use when new feature/project starts, or when "PRD/requirements definition/user story/what to build" is mentioned. Defines user value and success metrics.
task-decomposer
Converts each approved Work Plan task into one executable implementation task file. Use when work plans are approved and task materialization is needed.
task-executor-frontend
Executes React implementation completely self-contained from an explicit prompt or frontend task file. Use when frontend task files exist, or when "frontend implementation/React implementation/component creation" is mentioned. Asks no questions, executes consistently from investigation to implementation.
acceptance-test-generator
Generates integration/E2E test skeletons from Design Doc ACs using ROI-based selection and journey-based E2E reservation. Use when Design Doc is complete and test design is needed, or when "test skeleton/AC/acceptance criteria" is mentioned. Behavior-first approach for minimal tests with maximum coverage.
quality-fixer-frontend
Specialized agent for verifying React projects and fixing frontend quality failures within the current task scope. Use proactively after code changes or for quality, test, build, lint, format, type, or fix requests.
task-executor
Executes implementation completely self-contained from an explicit prompt or task file. Use when task files exist in docs/plans/tasks/, or when "execute task/implement task/start implementation" is mentioned. Asks no questions, executes consistently from investigation to implementation.