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/coffeecheese/easy-prd-testing/prd-intakenpx skills add CoffeeCheese/easy-prd-testing --skill prd-intakegit clone --depth 1 https://github.com/CoffeeCheese/easy-prd-testingWrote 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/skills/coffeecheese/easy-prd-testing/prd-intake)<a href="https://agentmods.dev/skills/coffeecheese/easy-prd-testing/prd-intake"><img src="https://agentmods.dev/badge/skills/coffeecheese/easy-prd-testing/prd-intake.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.1 | $0.00032 | $0.00424 |
| Opus 5 | $0.00016 | $0.00212 |
| Sonnet 5 | $0.00006 | $0.00085 |
| Haiku 4.5 | $0.00003 | $0.00042 |
Grade A, and why
prd-intake 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 5d 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
PRD Intake
Goal
Convert PRD, prototype, field baseline, or product notes into a clarified source understanding for test planning.
Input Gate
At least one of these inputs is required:
- PRD document.
- Prototype image or prototype link.
- Field baseline.
- User-provided product notes.
If none is available, ask for the source material and stop.
If the module name is missing, ask for the module name and do not create directories.
Analysis Rules
Extract:
- Module boundary.
- Dependent modules.
- External jumps.
- Feature points.
- Query fields.
- List fields.
- Detail fields.
- Buttons.
- Dialog fields.
- Permission requirements.
- High-risk actions.
- Test data assumptions.
Mark each extracted item with its source: PRD, prototype, field baseline, or user supplement.
When PRD and prototype conflict, treat the PRD as the default source and list the conflict as pending confirmation.
Anything inferred only from a prototype must be marked as pending user confirmation.
Clarification Rules
Ask one clarification question at a time. Do not combine unrelated missing information in one message.
Prefer asking about the earliest blocker:
- Module name.
- Module boundary.
- Field meaning or missing field source.
- Permission or role requirement.
- High-risk action behavior.
- Test data assumption.
Output
When enough information exists for planning, produce a concise intake summary.
Create 00-资料分析与待确认问题.md only after both module name and output root directory are confirmed. The file must be placed under:
<output-root>/easy-prd-testing/testing/<module-name>/
If the output root is not confirmed, output the intake summary in chat only and do not create files.
Do not generate 01-04; that belongs to test-planning.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 74 lines · 32 tokens per session scan A e2bbca9ebe91
prd-intake is a skill published in the GitHub repository CoffeeCheese/easy-prd-testing (2 stars, last pushed 24d ago), licensed MIT. It adds 32 tokens to every session and 424 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
add-community-extension
Add a community extension to the Spec Kit catalog from a GitHub issue submission. USE FOR: processing extension submission issues, validating catalog entries, updating catalog.community.json and docs/community/extensions.md, creating PRs. DO NOT USE FOR: creating new extensions from scratch, or first-party extension…
openspec-explore
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
release-openspec
Use this skill when releasing OpenSpec: audit merged work and changeset coverage, decide whether a catch-up changeset PR is needed, prepare or resume the Changesets Version Packages PR, cut a beta or stable release, verify publishing, and polish GitHub release notes. Also use when asked whether an open release PR is…
playwright-dev
Explains how to develop Playwright - add APIs, MCP tools, CLI commands, and vendor dependencies.
openspec-apply-change
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
openspec-update-change
Update an OpenSpec change by revising its existing planning artifacts and keeping them coherent with one another. Use when the user wants to revise a change's plan, fold new decisions into it, or reconcile its artifacts after an edit. Never edits code.