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 skills add The-AI-Directory-Company/agents-and-skills --skill test-plan-writinggit clone --depth 1 https://github.com/The-AI-Directory-Company/agents-and-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/skills/the-ai-directory-company/agents-and-skills/test-plan-writing)<a href="https://agentmods.dev/skills/the-ai-directory-company/agents-and-skills/test-plan-writing"><img src="https://agentmods.dev/badge/skills/the-ai-directory-company/agents-and-skills/test-plan-writing/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/skills/the-ai-directory-company/agents-and-skills/test-plan-writing"><img src="https://agentmods.dev/badge/skills/the-ai-directory-company/agents-and-skills/test-plan-writing.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.00038 | $0.01427 |
| Opus 5 | $0.00019 | $0.00714 |
| Sonnet 5 | $0.00008 | $0.00285 |
| Haiku 4.5 | $0.00004 | $0.00143 |
Grade A, and why
test-plan-writing 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 9d 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Plan Writing
Before you start
Gather the following from the user. If anything is missing, ask before proceeding:
- What is being tested? (Feature, service, migration, integration, or full release)
- What are the requirements? (Link to PRD, tickets, or acceptance criteria)
- What is the risk profile? (User-facing? Payment flow? Data migration? First launch or incremental?)
- What is the tech stack? (Languages, frameworks, third-party integrations, data stores)
- What testing infrastructure exists? (CI pipeline, staging environments, test data factories)
- What is the timeline? (Release date, testing window, hard deadlines)
Test plan template
1. Scope
Define what is in scope and what is explicitly out of scope. Every out-of-scope item should explain why (separate ticket, future phase, unchanged).
2. Risk Analysis
Rank components by risk. This drives where you invest testing effort.
| Component | Likelihood | Impact | Risk Level | Testing Investment |
|---|---|---|---|---|
| Payment processing | Medium | Critical | High | Extensive |
| Cart calculations | Low | High | Medium | Moderate |
| Confirmation page | Low | Low | Low | Minimal |
Rules:
- Anything involving money, PII, or data loss is automatically High impact
- New third-party integrations are Medium likelihood minimum
- Components with no existing test coverage get a likelihood bump
3. Test Levels per Component
For each component, decide which test levels apply and why.
| Component | Unit | Integration | E2E | Manual | Rationale |
|---|---|---|---|---|---|
| Price calculation | Yes | No | No | No | Pure logic, no external deps |
| Stripe integration | No | Yes | Yes | No | Must verify real API contract |
| Checkout flow | No | No | Yes | Yes | User-facing critical path |
Key principle: test at the lowest level that gives you confidence. Unit tests for logic, integration tests for contracts, E2E for critical user journeys only.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 142 lines · 38 tokens per session scan A 19e69f1abdaa
test-plan-writing is a skill published in the GitHub repository The-AI-Directory-Company/agents-and-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 38 tokens to every session and 1,427 once invoked, about $0.0002 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 skills, from other repositories
testing-strategy
Follow the testing pyramid — more unit tests, fewer integration tests, even fewer e2e tests.
ds-test
Universal test skill — generate, update, run, and fix tests for any stack. Use when writing, repairing, or running tests, or improving coverage.
testing-strategy
Comprehensive testing expertise across unit, integration, and e2e tests. Covers pytest, Vitest, Jest, Go testing, Playwright, Cypress. Test pyramids, TDD workflow, mocking patterns, coverage targets, property-based testing, snapshot testing, parameterized tests, fixtures, CI integration. Use when writing tests…
webapp-testing
Write and run comprehensive web app tests — unit, integration, E2E with Playwright/Cypress, and visual regression.
memstack-development-test-writer
Use this skill when the user says 'write tests', 'add tests', 'test coverage', 'unit tests', 'integration tests', 'component tests', 'mocking', 'edge cases', or needs to generate tests with proper mocking and edge case coverage. Do NOT use for refactoring plans or database migrations.
testing-patterns
Testing strategy: pyramid, AAA, mocks/fakes/stubs, flaky tests, coverage. Triggers: test, fixture, mock, stub, e2e, TDD, Playwright, Cypress, flaky, coverage, property-based.