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/latestaiagents/agent-skills/test-plangit clone --depth 1 https://github.com/latestaiagents/agent-skillsWrote 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/latestaiagents/agent-skills/test-plan)<a href="https://agentmods.dev/commands/latestaiagents/agent-skills/test-plan"><img src="https://agentmods.dev/badge/commands/latestaiagents/agent-skills/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.00012 | $0.00321 |
| Opus 5 | $0.00006 | $0.00161 |
| Sonnet 5 | $0.00002 | $0.00064 |
| Haiku 4.5 | $0.00001 | $0.00032 |
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 yesterday.
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.
What it actually says
/test-plan
Create a comprehensive test plan for your project or release.
What I Need
Tell me:
- Project/feature being tested
- Timeline and milestones
- Team size and roles
- Risk areas
- Environment details
What I'll Create
A complete test plan including:
- Scope - What's in/out of testing
- Approach - Test levels and types
- Schedule - Timeline with milestones
- Resources - People, environments, tools
- Risks - Potential issues and mitigation
- Criteria - Entry/exit conditions
- Deliverables - Reports and artifacts
Template Sections
1. Introduction & Objectives
2. Scope (In/Out)
3. Test Strategy
4. Test Environment
5. Test Data Requirements
6. Schedule & Milestones
7. Resource Allocation
8. Risk Assessment
9. Entry/Exit Criteria
10. Deliverables
Example
You: /test-plan
Project: E-commerce checkout redesign
Timeline: 4 weeks
Team: 2 QA engineers
Risks: Payment integration, mobile compatibility
Claude: [Generates complete test plan with schedule,
resource allocation, risk matrix, environment setup,
test types coverage, and success criteria]
Output
Full document ready for:
- Stakeholder review
- Team alignment
- Project tracking
- Audit compliance
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.
- yesterday First seen · 67 lines · 12 tokens per session scan A 6f710f096ae5
test-plan is a command published in the GitHub repository latestaiagents/agent-skills (5 stars, last pushed 4mo ago), licensed MIT. It adds 12 tokens to every session and 321 once invoked, about $0.0001 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-09-03.
Other commands, from other repositories
fdk-react-create
Create a new Platform 3.0 React Meta app (default UI stack). Uses fdk create react-starter-template or react-meta skeletons with DEW components, metaConfig in manifest.json, and React Router.
fdk-refactor
Reduce function complexity in a Freshworks app to meet cyclomatic complexity ≤ 7 per function. Extracts helper functions, simplifies conditionals, and preserves behavior while improving code quality.
fw-setup-uninstall
Uninstall FDK completely — keeps Node.js and nvm (/fw-setup uninstall).
fw-setup-troubleshoot
Diagnose FDK / nvm / shell PATH; optional --fix runs automated repair Task; on failure switches to interactive human-guided SOP mode.
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.