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/danielvm-git/bigpowers/plan-testsnpx skills add danielvm-git/bigpowers --skill plan-testsgit clone --depth 1 https://github.com/danielvm-git/bigpowersWhat 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.00038 | $0.00732 |
| Opus 5 | $0.00019 | $0.00366 |
| Sonnet 5 | $0.00008 | $0.00146 |
| Haiku 4.5 | $0.00004 | $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 2d 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 — 76 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.
- 2d ago First seen · 76 lines · 38 tokens per session scan A bf2bfb3eae96
plan-tests is a skill published in the GitHub repository danielvm-git/bigpowers (156 stars, last pushed 25d ago), licensed MIT. It adds 38 tokens to every session and 732 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-30.
Other skills, from other repositories
shared/tech-stack-detection
检测项目技术栈的通用方法，通过分析配置文件识别语言、框架、工具链.
devops/changelog-generation
自动生成 CHANGELOG，基于 git 提交历史和 pipeline 产物信息，遵循 Conventional Commits 和 Keep a Changelog 规范.
boss
可审计的 agent 团队：BMAD 全自动研发流水线编排器。编排 9 个专业 Agent（PM、架构师、UI Designer、Tech Lead、Scrum Master、Frontend、Backend、QA、DevOps）从需求到部署，每一步都有事件溯源 + 不可绕过门禁 + 确定性 eval——可验证测试真跑、门禁真过。支持单环节切片命令（/boss:plan /review /qa /ship）与无 CLI 纯 Markdown 降级。 Triggers: 'boss mode', '/boss', '全自动开发', '从需求到部署', '帮我做一个', 'build this', 'ship it', '全流程'…
debloat
Compress an artifact that has accreted into bloat — padding, over-qualification, fused sentences, walls of enumeration, adjacent restatement — down to its load-bearing density, meaning preserved. Use when prose is correct and current but has grown verbose or patched-over and you want it tight without a full rewrite.
bmad-dev-story
Execute story implementation following a context filled story spec file. Use when the user says "dev this story [story file]" or "implement the next story in the sprint plan".
bmad-validate-prd
Validate a PRD against standards. Use when the user says "validate this PRD" or "run PRD validation".