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 rules/danielvm-git/bigpowers/plan-testsgit clone --depth 1 https://github.com/danielvm-git/bigpowersWrote 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/rules/danielvm-git/bigpowers/plan-tests)<a href="https://agentmods.dev/rules/danielvm-git/bigpowers/plan-tests"><img src="https://agentmods.dev/badge/rules/danielvm-git/bigpowers/plan-tests.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 | $0.00035 | $0.00728 |
| Opus 5 | $0.00017 | $0.00364 |
| Sonnet 5 | $0.00007 | $0.00146 |
| Haiku 4.5 | $0.00003 | $0.00073 |
Grade A, and why
plan-tests 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 today.
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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Tests
Spine position: Between
slice-tasksandplan-workfor epics withrisk: P0|P1. Optional (can be waived instate.yaml) for P2/P3.
Bridges the gap between slicing and planning by systematically designing the test suite as a first-class system. Produces specs/tech-architecture/eNN-TEST_PLAN_LATEST.md.
Pre-flight
- Read
specs/epics/eNN-*/story list.
Core Workflow
- Analyze Epic: Read sliced stories in the active epic capsule.
- Risk Assessment: Map behaviors to P0–P3 risk tiers.
- Level Strategy: Classify each scenario (Unit, Integration, E2E).
- Fixture Design: Plan factories, network intercepts, mocks (see REFERENCE.md).
- NFR Plan: Define verifiable commands for Non-Functional Requirements. Skip if
--lite. - Publish: Generate
specs/tech-architecture/eNN-TEST_PLAN_LATEST.md.
Hard Gates & Guardrails
- DO NOT write test code or production code during this skill.
- Scenario ID format MUST be:
SC-eNNsYY-P{0|1|2|3}-NN. plan-workMUST reference these scenario IDs in its §17 Gherkin acceptance criteria.- Default to pushing tests to the lowest possible level.
Execution Modes
$bmad plan-tests: Standard execution.$bmad plan-tests --lite: Skips NFRs and complex fixture planning.
Verify
→ verify: test -f specs/tech-architecture/e32-TEST_PLAN_LATEST.md
Handoff
Gate: READY -> next: plan-work Writes: state.yaml handoff.next_skill = plan-work
Plan Tests — Reference
Test Plan Template (specs/tech-architecture/eNN-TEST_PLAN_LATEST.md)
# Test Design: [eNN-slug]
## 1. Risk Matrix & Scenarios
| Scenario ID | Behavior Description | Risk | Test Level | Target File/Module |
|-------------|----------------------|------|------------|--------------------|
| SC-P0-01 | Primary checkout | P0 | Integration | checkout.spec.ts |
## 2. Fixture Architecture & Isolation
- Data Factories: (e.g. UserFactory)
- Network Intercepts: (e.g. MSW handlers)
- Database State: (e.g. in-memory SQLite)
## 3. NFR Verification
| NFR Type | Requirement | Verification Command |
|----------|-------------|----------------------|
| Perf | < 200ms | `npm run test:perf` |
## 4. Out of Scope
- [Explicitly excluded testing areas]
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.
- today First seen · 75 lines · 35 tokens per session scan A c4ac2e69ffec
plan-tests is a cursor rule published in the GitHub repository danielvm-git/bigpowers (163 stars, last pushed 2d ago), licensed MIT. It adds 35 tokens to every session and 728 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-09-03.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
app-router-patterns
Next.js 14+ App Router patterns — Server Components, Client Components, Route Handlers, Server Actions, and metadata API.
00-project-rules
ContextOS core project rules and role orchestration.
context-os
ContextOS rules for context-os.
database
Database architecture, schema design, Prisma, Drizzle ORM, indexing strategies, migrations, and N+1 query resolution.
vue
Rules for Vue (2 and 3) single-file components.