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 latestaiagents/agent-skills --skill test-planninggit 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/skills/latestaiagents/agent-skills/test-planning)<a href="https://agentmods.dev/skills/latestaiagents/agent-skills/test-planning"><img src="https://agentmods.dev/badge/skills/latestaiagents/agent-skills/test-planning/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/latestaiagents/agent-skills/test-planning"><img src="https://agentmods.dev/badge/skills/latestaiagents/agent-skills/test-planning.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.00051 | $0.01412 |
| Opus 5 | $0.00026 | $0.00706 |
| Sonnet 5 | $0.00010 | $0.00282 |
| Haiku 4.5 | $0.00005 | $0.00141 |
Grade A, and why
test-planning 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 — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Planning
Create comprehensive test strategies that ensure quality and coverage.
When to Use
- Planning testing for a new feature or release
- Creating a test strategy document
- Defining test coverage requirements
- Estimating testing effort
- Setting up QA processes for a new project
Test Strategy Document Template
# Test Strategy: [Project/Feature Name]
**Version:** 1.0
**Author:** [Name]
**Date:** [Date]
**Status:** Draft / In Review / Approved
## 1. Introduction
### 1.1 Purpose
[Brief description of what this test strategy covers]
### 1.2 Scope
**In Scope:**
- [Feature/component 1]
- [Feature/component 2]
**Out of Scope:**
- [Explicitly excluded items]
### 1.3 References
- PRD: [link]
- Technical Design: [link]
- API Specs: [link]
## 2. Test Objectives
- Verify [functional requirement 1]
- Validate [performance requirement]
- Ensure [security requirement]
- Confirm [compatibility requirement]
## 3. Test Approach
### 3.1 Test Levels
| Level | Scope | Owner | Tools |
|-------|-------|-------|-------|
| Unit | Individual functions | Dev | Jest, pytest |
| Integration | API contracts | Dev/QA | Postman, SuperTest |
| E2E | User workflows | QA | Playwright, Cypress |
| Performance | Load/stress | QA | k6, Artillery |
### 3.2 Test Types
- [ ] Functional testing
- [ ] Regression testing
- [ ] Smoke testing
- [ ] Integration testing
- [ ] Performance testing
- [ ] Security testing
- [ ] Accessibility testing
- [ ] Compatibility testing
## 4. Test Environment
| Environment | Purpose | Data |
|-------------|---------|------|
| Dev | Unit/Integration | Mocked |
| Staging | E2E/Regression | Sanitized prod |
| Pre-prod | Performance/Security | Prod-like |
## 5. Test Data
### Requirements
- [Data requirement 1]
- [Data requirement 2]
### Sources
- Test data generators
- Sanitized production data
- Synthetic data sets
## 6. Entry/Exit Criteria
### Entry Criteria
- [ ] Code complete and merged
- [ ] Unit tests passing (>80% coverage)
- [ ] Environment deployed and stable
- [ ] Test data prepared
### Exit Criteria
- [ ] All critical test cases passed
- [ ] No P0/P1 bugs open
- [ ] Performance benchmarks met
- [ ] Security scan passed
- [ ] Sign-off from stakeholders
## 7. Risk Assessment
| Risk | Likelihood | Impact | Mitigation |
|------|------------|--------|------------|
| [Risk 1] | High/Med/Low | High/Med/Low | [Action] |
| [Risk 2] | | | |
## 8. Schedule
| Phase | Start | End | Owner |
|-------|-------|-----|-------|
| Test Planning | | | |
| Test Case Design | | | |
| Test Execution | | | |
| Bug Fixing | | | |
| Regression | | | |
| Sign-off | | | |
## 9. Deliverables
- [ ] Test cases in [TestRail/Xray]
- [ ] Automated test suite
- [ ] Test execution report
- [ ] Bug report summary
- [ ] Sign-off document
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 · 232 lines · 51 tokens per session scan A 129eefbadeea
test-planning is a skill published in the GitHub repository latestaiagents/agent-skills (5 stars, last pushed 4mo ago), licensed MIT. It adds 51 tokens to every session and 1,412 once invoked, about $0.0003 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
quality-hooks
Language-specific auto-lint/format/typecheck pipeline. Supports Python (ruff+pyright), TypeScript (prettier+eslint+tsc), Go (gofmt+golangci-lint). Auto-fix and convergence loops.
hook-management
Session-scoped hook lifecycle management with enable/disable/status controls, execution profiling, and color-coded performance alerts.
test-automation
Execute Vitest and Playwright test suites with result collection and failure analysis.
qa-testing
Generate and execute API and E2E tests with quality gate assessment.
story-development
Implement user stories with test-driven development methodology.
test-automation
Plan, write, and review automated tests following KATA (Komponent Action Test Architecture) on Playwright + TypeScript, or explain existing automated tests in a sealed read-only mode. Use when writing E2E or API/integration tests, creating Page or Api components, designing ATCs, parameterizing test data, registering…