test_plan.template

test_plan.template is a command for coding agents from Fomo-Driven-Development/strategic-claude-base. It costs 0 tokens per session (1,210 once invoked), scanned A, original, MIT.

A reusable test-plan template for a software feature or task. It organizes the implementation reference, current test coverage, required test types, testing approach, and out-of-scope areas.

In plain words
What is it for?
Use it to document unit, integration, end-to-end, performance, and security tests, including the files, test cases, and phases involved.
Why use it?
It gives a consistent way to find missing tests and define the testing work before implementation. It also helps prevent unplanned testing from expanding the task.

Command

Install

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.

agentmods
npx agentmods add commands/fomo-driven-development/strategic-claude-base/test_plan.template
Clone the repo
git clone --depth 1 https://github.com/Fomo-Driven-Development/strategic-claude-base

Wrote 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.

agentmods badge for test_plan.template

README.md
[![agentmods](https://agentmods.dev/badge/commands/fomo-driven-development/strategic-claude-base/test_plan.template.svg)](https://agentmods.dev/commands/fomo-driven-development/strategic-claude-base/test_plan.template)
Your own site
<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>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,210 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 5d ago against content hash 8be2da680359, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

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.

.strategic-claude-basic/templates/commands/test_plan.template.md · 217 lines

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

Read the full file on GitHub · 217 lines

Changes

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.

  1. 5d ago First seen · 217 lines · 0 tokens per session scan A 8be2da680359

Subscribe to this mod's changes

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.