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/check-prd-alignmentnpx skills add ChatPRD/cursor-plugin --skill check-prd-alignmentgit 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.00040 | $0.00535 |
| Opus 5 | $0.00020 | $0.00267 |
| Sonnet 5 | $0.00008 | $0.00107 |
| Haiku 4.5 | $0.00004 | $0.00053 |
Grade A, and why
check-prd-alignment 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.
How it starts
The opening of the file, as written. The whole thing — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Check PRD alignment
Trigger
User wants to verify their implementation matches the product requirements and find opportunities to better achieve the PRD's goals.
Workflow
- Identify what changed — run
git diffagainst the base branch to see all modifications. - Find the relevant PRD:
- Ask the user which PRD to check against.
- Search ChatPRD documents using
search_documentswith keywords from the branch or commit messages. - Also check the local
prd/directory for saved specs.
- Fetch the full PRD using
get_document. - Extract all requirements, acceptance criteria, and — critically — the user and business goals the PRD is trying to achieve.
- For each requirement, assess:
- Covered: implemented and matching the spec
- Partial: started but incomplete or missing edge cases
- Missing: not addressed in the current changes
- Deviated: implemented differently than specified
- Review the implementation through the lens of the PRD's stated goals. For each goal, identify Opportunity items — places where the UX or implementation could be improved to better achieve the goal. Examples:
- A flow that technically meets the spec but adds unnecessary friction
- An edge case where a better error message or fallback would improve the experience
- A place where the implementation could be more delightful or intuitive than what was specced
- A data model or API design choice that would better support the stated business goal
- Produce a coverage report with:
- Requirement-by-requirement status
- Specific code references for covered items
- Actionable notes for gaps and deviations
- Opportunity items tied back to specific PRD goals
Guardrails
- Be specific — cite file paths and line ranges, not vague summaries.
- Distinguish between intentional trade-offs and accidental omissions.
- Don't flag requirements that are explicitly marked as out-of-scope or future work in the PRD.
- Keep Opportunity items grounded and actionable — tie each one to a specific PRD goal and explain the concrete improvement.
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 · 50 lines · 40 tokens per session scan A 3ba3b07f9599
check-prd-alignment is a skill published in the GitHub repository ChatPRD/cursor-plugin (5 stars, last pushed 6mo ago), licensed MIT. It adds 40 tokens to every session and 535 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…