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 skills/chatprd/cursor-plugin/implement-from-prdnpx skills add ChatPRD/cursor-plugin --skill implement-from-prdgit clone --depth 1 https://github.com/ChatPRD/cursor-pluginWhat 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.00047 | $0.00395 |
| Opus 5 | $0.00023 | $0.00198 |
| Sonnet 5 | $0.00009 | $0.00079 |
| Haiku 4.5 | $0.00005 | $0.00040 |
Grade A, and why
implement-from-prd 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 2d 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
Implement from PRD
Trigger
User has a PRD in ChatPRD and wants to plan or start the implementation.
Workflow
- Help the user find the right PRD:
- Search documents using
search_documentsif they give a name or keyword. - Or list recent documents using
list_documentsto browse. - Also check the local
prd/directory for previously saved specs.
- Search documents using
- Fetch the full PRD content using
get_document. - Enter plan mode to build the implementation plan. The plan should:
- Analyze the codebase to understand where new code should live, what can be reused, and what conventions to follow.
- Break the PRD into implementation milestones, each a shippable increment ordered by dependency (schema → API → UI).
- For each milestone, specify: files to create or modify, key implementation details, acceptance criteria from the PRD, and risks or unknowns.
- Map every PRD requirement to at least one milestone so nothing is missed.
- Present the plan for the user to review and approve before starting implementation.
- Once approved, begin work on the first milestone.
Guardrails
- Always use plan mode — never jump straight to implementation on a PRD.
- Map every PRD requirement to at least one milestone.
- Flag requirements that are ambiguous or missing technical detail.
- Keep milestones small enough to review in a single PR.
- Don't skip edge cases mentioned in the PRD.
Output
- Implementation plan with ordered milestones
- File-level change list per milestone
- Requirement coverage mapping
- Ready to execute on first milestone after approval
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.
- 2d ago First seen · 41 lines · 47 tokens per session scan A 2895678c5d0c
implement-from-prd is a skill published in the GitHub repository ChatPRD/cursor-plugin (5 stars, last pushed 6mo ago), licensed MIT. It adds 47 tokens to every session and 395 once invoked, about $0.0002 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…