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/thedecipherist/claude-code-mastery-project-starter-kit/test-plangit clone --depth 1 https://github.com/TheDecipherist/claude-code-mastery-project-starter-kitWrote 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/thedecipherist/claude-code-mastery-project-starter-kit/test-plan)<a href="https://agentmods.dev/commands/thedecipherist/claude-code-mastery-project-starter-kit/test-plan"><img src="https://agentmods.dev/badge/commands/thedecipherist/claude-code-mastery-project-starter-kit/test-plan.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.00008 | $0.00674 |
| Opus 5 | $0.00004 | $0.00337 |
| Sonnet 5 | $0.00002 | $0.00135 |
| Haiku 4.5 | $0.00001 | $0.00067 |
Grade A, and why
test-plan 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Plan Generator
Create a structured test plan for: $ARGUMENTS
Auto-Branch (if on main)
Before creating test plan files, check the current branch:
git branch --show-current
Default behavior (auto_branch = true in claude-mastery-project.conf):
- If on
mainormaster: automatically create a feature branch and switch to it:
Report: "Created branchgit checkout -b test/<feature-name>-plantest/<feature>-plan— main stays untouched." - If already on a feature branch: proceed
- If not a git repo: skip this check
To disable: Set auto_branch = false in claude-mastery-project.conf. When disabled, warn and ask the user before proceeding on main.
Template
Generate the following markdown document:
# [Feature] Test Plan
**Created:** [today's date]
**Feature:** $ARGUMENTS
**Status:** ⬜ Not Started
---
## Quick Status
Feature Area A: ⬜ NOT TESTED
Feature Area B: ⬜ NOT TESTED
Feature Area C: ⬜ NOT TESTED
---
## Prerequisites
- [ ] Required services running
- [ ] Test data created
- [ ] Environment variables set
---
## Test 1: [Happy Path]
### 1.1 [Core scenario]
**Action:** [What to do]
**Expected:** [What should happen — be SPECIFIC]
| Check | Expected | Actual | Status |
|-------|----------|--------|--------|
| Response code | 200 | | ⬜ |
| Data returned | [specific shape] | | ⬜ |
| UI updated | [specific change] | | ⬜ |
---
## Test 2: [Error Cases]
### 2.1 [Invalid input]
**Action:** [What to do]
**Expected:** [Specific error message/behavior]
---
## Test 3: [Edge Cases]
### 3.1 [Empty state]
### 3.2 [Maximum values]
### 3.3 [Concurrent access]
---
## Pass/Fail Criteria
| Criteria | Pass | Fail |
|----------|------|------|
| All happy paths work | Yes | Any failure |
| Error messages shown | Yes | Silent failure |
| Data persists | Yes | Lost on refresh |
---
## Sign-Off
| Test | Tester | Date | Status |
|------|--------|------|--------|
| Test 1 | | | ⬜ |
| Test 2 | | | ⬜ |
| Test 3 | | | ⬜ |
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 · 119 lines · 8 tokens per session scan A 6f175cf1c2d7
test-plan is a command published in the GitHub repository TheDecipherist/claude-code-mastery-project-starter-kit (337 stars, last pushed 2mo ago), licensed MIT. It adds 8 tokens to every session and 674 once invoked, about $0.0000 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.
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.