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/test-planningnpx skills add CoffeeCheese/easy-prd-testing --skill test-planninggit 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/test-planning)<a href="https://agentmods.dev/skills/coffeecheese/easy-prd-testing/test-planning"><img src="https://agentmods.dev/badge/skills/coffeecheese/easy-prd-testing/test-planning.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.00028 | $0.00480 |
| Opus 5 | $0.00014 | $0.00240 |
| Sonnet 5 | $0.00006 | $0.00096 |
| Haiku 4.5 | $0.00003 | $0.00048 |
Grade A, and why
test-planning 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
Test Planning
Goal
Generate executable automation self-testing planning artifacts from confirmed PRD/prototype understanding.
Required Inputs
- Module name.
- PRD/prototype/field baseline/product notes, or an intake summary from
prd-intake. - Output root directory confirmed by the user.
Output Directory Gate
Before creating files, ask where automation testing results and planning artifacts should be written.
All files must be placed under:
<output-root>/easy-prd-testing/testing/<module-name>/
Do not default to the repository docs/ directory unless the user explicitly chooses it as the output root.
Generated Artifacts
Create or update:
01-模块拆解.md02-测试用例.md03-执行清单.md04-测试数据与账号.md
Planning Rules
- Feature IDs use
F-xxx. - Every test case links to at least one
F-xxxfeature ID defined in01-模块拆解.md. - Test case IDs use
<module-code>-P<priority>-NNN. - Priorities are
P0,P1,P2, andP3. - Each case records its execution directory:
执行结果/P0/,执行结果/P1/,执行结果/P2/, or执行结果/P3/. - Field baselines record their source.
- Prototype-only fields are marked pending user confirmation.
Optional XMind Review Artifact
After generating or updating 01-04, ask whether the user wants the optional native 02-测试用例.xmind review artifact. If the user opts in, use xmind-export before requesting final planning confirmation.
- Do not generate the XMind without user opt-in.
- Do not treat the XMind as an authoritative source or gate requirement.
- Do not block confirmation of valid
01-04files when the export is skipped or fails.
Stop Condition
After offering or completing the optional XMind export, stop and ask the user to explicitly confirm the 01-04 planning artifacts. Do not enter execution gates automatically.
What ships with it
4 files 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 · 60 lines · 28 tokens per session scan A 45018b842416
test-planning is a skill published in the GitHub repository CoffeeCheese/easy-prd-testing (2 stars, last pushed 23d ago), licensed MIT. It adds 28 tokens to every session and 480 once invoked, about $0.0001 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-verify-change
Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.