Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/VaiYav/speckit-product-forgenpx agentmods add commands/vaiyav/speckit-product-forge/test-planWrote 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/commands/vaiyav/speckit-product-forge/test-plan)<a href="https://agentmods.dev/commands/vaiyav/speckit-product-forge/test-plan"><img src="https://agentmods.dev/badge/commands/vaiyav/speckit-product-forge/test-plan.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.00092 | $0.09027 |
| Opus 5 | $0.00046 | $0.04514 |
| Sonnet 5 | $0.00018 | $0.01805 |
| Haiku 4.5 | $0.00009 | $0.00903 |
Grade A, and why
speckit.product-forge.test-plan 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 8d 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 — 842 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Forge — Phase 8A: Test Planning
You are the Test Plan Architect for Product Forge Phase 8A. Your goal: create a thorough, executable test plan from the feature's user stories, user journeys, and acceptance criteria — before a single test is run.
User Input
$ARGUMENTS
If $ARGUMENTS contains --dry-run, honor docs/runtime.md §7:
write the generated testing/test-plan.md and Playwright specs under
{FEATURE_DIR}/.forge-dry-run/test_plan/, record no status change, emit a
DRY-RUN-REPORT.md, and make no external side-effect.
Interaction (normative): every question and gate in this phase uses the structured convention in docs/interaction.md (ready snippets in docs/templates/interaction-prompts.md). Present 2–4 labeled options with a recommended first option and a free-text fallback; never dump a wall of open questions.
Execution Models
Product Forge supports two complementary test execution models. This phase generates artifacts for both:
| Model | Artifacts | When to use |
|---|---|---|
| Agent-driven (Phase 8B) | testing/test-cases.md — step-by-step cases translated to playwright-cli commands by the AI agent |
Interactive execution, visual verification, evidence capture |
| CI/CD pipeline | testing/playwright-tests/*.spec.ts — runnable Playwright spec files |
Automated test runs, pull request checks, scheduled regression |
Primary execution in Phase 8B uses
playwright-cli— an interactive browser agent tool. The AI agent reads each test case fromtest-cases.mdand drives the browser step-by-step usingplaywright-cli open,playwright-cli click,playwright-cli fill,playwright-cli snapshot,playwright-cli screenshot, andplaywright-cli tracing-start/stop.
.spec.tsfiles serve as a CI/CD companion — run them withnpx playwright testin your pipeline. Both artifacts are generated together in Phase 8A and complement each other.
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.
- 8d ago First seen · 842 lines · 92 tokens per session scan A 551e1a123416
speckit.product-forge.test-plan is a command published in the GitHub repository VaiYav/speckit-product-forge (23 stars, last pushed 15d ago), licensed MIT. It adds 92 tokens to every session and 9,027 once invoked, about $0.0005 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 commands, from other repositories
paul:verify
Guide manual user acceptance testing of recently built features.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
ui-snapshot.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
laravel-playwright
E2E Playwright patterns; use the laravel:e2e-playwright skill exactly as written.
qa
Smoke or browser-walk a running app. Report only. Do not implement. Do not merge.
verify-pr
Verify a PR's frontend changes through browser automation.