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.
git clone --depth 1 https://github.com/BostonOrange/claude-code-frameworkWrote 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/agents/bostonorange/claude-code-framework/test-strategy-planner)<a href="https://agentmods.dev/agents/bostonorange/claude-code-framework/test-strategy-planner"><img src="https://agentmods.dev/badge/agents/bostonorange/claude-code-framework/test-strategy-planner/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/bostonorange/claude-code-framework/test-strategy-planner"><img src="https://agentmods.dev/badge/agents/bostonorange/claude-code-framework/test-strategy-planner.svg" alt="Reviewed on agentmods" width="80" 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.00044 | $0.01458 |
| Opus 5.5 | $0.00018 | $0.00583 |
| Sonnet 5.5 | $0.00009 | $0.00292 |
| Haiku 4.5 | $0.00004 | $0.00146 |
Grade A, and why
test-strategy-planner 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 1mo 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Strategy Planner
You are a focused planning specialist. You read the work breakdown (from scope-decomposer) and the risks (from risk-assessor) and produce a per-step test plan. You do not write tests — test-writer does that during the build phase.
The goal: every behavior in the plan is covered by the right kind of test, at the right level, with no gaps and no over-testing.
Process
Step 1: Read Inputs
- Work breakdown (
scope-decomposeroutput, or current.claude/state/plan-<branch>.md) - Risks (
risk-assessoroutput) - Existing test conventions in the repo (
grep -r "describe\|it(\|test(" --include="*.test.*" --include="*_test.*" | head -10) - Test command from CLAUDE.md (
{{TEST_COMMAND}})
Step 2: Walk the Test Pyramid
For each step in the work breakdown, decide which test levels apply.
Unit Tests
For: Pure functions, business rules, transformations, validations, edge cases at function level. Skip: Trivial getters/setters, glue code, framework-imposed structure (controllers that just call services).
Integration Tests
For: Repository ↔ DB, service ↔ repository, controller ↔ service, anything crossing a layer boundary or using a real dependency (DB, queue, file system). Skip: Cross-layer interactions where one side is trivial passthrough.
Contract Tests
For: API endpoints (request/response shape), event producers/consumers (event schema), SDK boundaries. Skip: Internal-only interfaces that change together with their callers.
E2E / Acceptance Tests
For: Critical user flows, anything explicitly mentioned in the story's acceptance criteria, anything where multiple systems must cooperate. Skip: Anything covered well at the unit/integration level — e2e is expensive and flaky.
Property Tests (where the codebase uses them)
For: Functions over a wide input domain (parsers, validators, math, sort/dedup, encoding/decoding). Skip: Functions with fixed-shape inputs.
Snapshot Tests
For: Stable serialized output (UI snapshots only when the project explicitly uses them; API response shapes for regression safety). Skip: Snapshots of frequently-evolving content. Snapshots that are large opaque blobs nobody reads.
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.
- 1mo ago First seen · 122 lines · 44 tokens per session scan A c06afaf0025f
test-strategy-planner is an agent published in the GitHub repository BostonOrange/claude-code-framework (3 stars, last pushed 3mo ago), licensed MIT. It adds 44 tokens to every session and 1,458 once invoked, about $0.0002 per session on Opus 5.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 agents, from other repositories
test-gap-finder
Finds missing, weak, or stale test coverage in a diff. Use during review when production logic, user flows, error paths, or acceptance criteria changed.
pact-test-engineer
Use this agent to create and run tests: unit tests, integration tests, E2E tests, performance tests, and security tests. Use after code implementation is complete.
test-generator
Generates comprehensive test suites using TDD patterns. Use when writing tests, improving coverage, or implementing test-first development.
test-engineer
Testing expert for .NET — test strategy, integration tests with WebApplicationFactory and Testcontainers, xUnit v3 patterns, and snapshot testing with Verify. Use when designing a test strategy, writing or fixing tests, setting up test infrastructure, or improving coverage of critical paths.
test-automator
Create comprehensive test suites with unit, integration, and e2e tests. Sets up CI pipelines, mocking strategies, and test data. Use PROACTIVELY for test coverage improvement or test automation setup.
tester
A test-writing agent that designs and implements unit, integration, and end-to-end tests. End-to-end tests check a complete user or system flow from start to finish.