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 skills add mattgierhart/PRD-driven-context-engineering --skill prd-v07-test-planninggit clone --depth 1 https://github.com/mattgierhart/PRD-driven-context-engineeringWrote 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/mattgierhart/prd-driven-context-engineering/prd-v07-test-planning)<a href="https://agentmods.dev/skills/mattgierhart/prd-driven-context-engineering/prd-v07-test-planning"><img src="https://agentmods.dev/badge/skills/mattgierhart/prd-driven-context-engineering/prd-v07-test-planning/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/skills/mattgierhart/prd-driven-context-engineering/prd-v07-test-planning"><img src="https://agentmods.dev/badge/skills/mattgierhart/prd-driven-context-engineering/prd-v07-test-planning.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00125 | $0.03433 |
| Opus 5 | $0.00063 | $0.01716 |
| Sonnet 5 | $0.00025 | $0.00687 |
| Haiku 4.5 | $0.00013 | $0.00343 |
Grade A, and why
prd-v07-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 10d 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 — 366 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Planning
Position in workflow: v0.7 Epic Scoping → v0.7 Test Planning → v0.7 Implementation Loop
Consumes
This skill requires prior work from v0.7 Epic Scoping and v0.6 specifications:
- EPIC-* entries (from v0.7 Epic Scoping) — EPIC scope defines test boundaries; test plan must cover all APIs/BRs/UJs within EPIC Context & IDs section
- API-* endpoint contracts (from v0.6 Technical Specification) — Each endpoint has request/response shape and error codes that must be tested
- DBT-* data model specifications (from v0.6 Technical Specification) — Schema constraints, relationships, and business rules enforce data integrity tests
- BR-* business rules (from v0.3 Commercial Model) — Each rule must have at least one test verifying positive (rule allows) and negative (rule blocks) cases
- UJ-* user journey entries (from v0.4 User Journeys) — Critical journeys need E2E tests verifying complete flow from trigger to value moment
This skill assumes EPIC- entries are complete with full API-/DBT-/BR-/UJ- references in Context & IDs section.
Produces
This skill creates/updates:
- TEST-* entries (test case specifications, automation path) — Concrete, verifiable test cases with Given-When-Then format, test type, and coverage mapping to upstream IDs
- Test coverage matrix (per EPIC) — Validation showing every API- endpoint, BR- rule, and core UJ- journey has TEST- entries; identifies gaps
- Test automation specification — For each Critical/High priority TEST-, identifies test file path and automation framework (unit/integration/E2E)
All TEST- entries are acceptance criteria specifications, not confidence-based. They are:
- Derivable from upstream IDs (every TEST- ties to specific API-/BR-/UJ-/DBT-)
- Executable (Given-When-Then format is testable; automation paths are specified)
- Complete for acceptance (passing all TEST- for EPIC means EPIC is done)
- Focused on behavior (tests what the system does, not implementation details)
What ships with it
3 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.
- 10d ago First seen · 366 lines · 125 tokens per session scan A 21845ac3f328
prd-v07-test-planning is a skill published in the GitHub repository mattgierhart/PRD-driven-context-engineering (182 stars, last pushed 9d ago), licensed MIT. It adds 125 tokens to every session and 3,433 once invoked, about $0.0006 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-30.
Other skills, from other repositories
setup
Set up or update TDD Guard for the current project. Detects the test framework, installs or updates the matching reporter, and configures or migrates its configuration to match the current specification.
plan-pipeline-execute
Execute a validated plan: worktree isolation, TDD scaffolding, level-based parallel agents, quality gate with smoke test, PR creation and merge. Handles everything through to merged PR.
review-readiness-scan
A batch scanner that checks multiple active changes to see whether their manual-review sections are ready for inspection.
verification-create
Use when user requests verification setup. NOT for maintenance.
verification-maintain
Use when user requests verification maintenance. NOT for setup.
review-screenshot
A standard workflow for taking screenshots to check a user interface, using a dedicated review process for different verification modes.