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 commands/fomo-driven-development/strategic-claude-base/test_plan.templategit clone --depth 1 https://github.com/Fomo-Driven-Development/strategic-claude-baseWrote 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/fomo-driven-development/strategic-claude-base/test_plan.template)<a href="https://agentmods.dev/commands/fomo-driven-development/strategic-claude-base/test_plan.template"><img src="https://agentmods.dev/badge/commands/fomo-driven-development/strategic-claude-base/test_plan.template.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.00000 | $0.01210 |
| Opus 5 | $0.00000 | $0.00605 |
| Sonnet 5 | $0.00000 | $0.00242 |
| Haiku 4.5 | $0.00000 | $0.00121 |
Grade A, and why
test_plan.template 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.
How it starts
The opening of the file, as written. The whole thing — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
[Feature/Task Name] Test Plan
Overview
[Brief description of what we're testing and the testing approach]
Implementation Plan Reference
Related Implementation Plan: .strategic-claude-basic/plan/PLAN_[NNNN]_[date]_[subject].md
[Brief summary of what the implementation plan covers]
Current Test Coverage Analysis
[Assessment of existing tests, gaps in coverage, testing infrastructure state]
Test Strategy
Test Types Required:
- Unit Tests: [Components/functions to unit test]
- Integration Tests: [System interactions to test]
- End-to-End Tests: [User workflows to test]
- Performance Tests: [Load/stress testing requirements]
- Security Tests: [Security validation requirements]
Testing Approach:
[High-level strategy for test implementation]
What We're NOT Testing
[Explicitly list out-of-scope testing areas to prevent scope creep]
Phase 1: [Test Type/Area]
Overview
[What this test phase accomplishes]
Test Coverage Requirements:
1. [Component/Feature Group]
Files Under Test: path/to/file.ext
Test File: path/to/test/file_test.ext
Test Cases:
// Example test structure
describe('[Component Name]', () => {
test('should [behavior]', () => {
// Test implementation
});
});
Coverage Requirements:
- Happy path scenarios
- Edge cases and error conditions
- Input validation
- Error handling
Test Data and Fixtures:
Test Data Requirements:
- [Data setup needed]
- [Fixture files to create]
- [Mock data patterns]
Test Environment Setup:
- [Database setup/teardown]
- [External service mocking]
- [Configuration requirements]
Success Criteria:
Automated Verification:
- Test suite runs successfully:
[test command] - Coverage threshold met:
[coverage command] - No test flakiness:
[stability test command] - Tests pass in CI environment:
[ci test command]
Manual Verification:
- Tests accurately validate expected behavior
- Edge cases are properly covered
- Test output is clear and actionable
- Test execution time is acceptable
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 · 217 lines · 0 tokens per session scan A 8be2da680359
test_plan.template is a command published in the GitHub repository Fomo-Driven-Development/strategic-claude-base (2 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,210 tokens. 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.