test-plan

test-plan is a skill for Claude Code, Codex from clawpod-app/awesome-openclaw-agent-packs. It costs 47 tokens per session (372 once invoked), scanned A, original, no licence file.

A test-plan writing guide that describes test cases, edge cases, and the conditions a feature must meet.

In plain words
What is it for?
Use it to plan quality checks, write test cases, and create acceptance criteria or a QA checklist.
Why use it?
It helps teams find overlooked failure scenarios and agree on what counts as working.

Skill for Claude CodeCodex

Which agent this was written for is unclear — body not stored (licence); the path alone says nothing.

Good fit Use it to plan quality checks, write test cases, and create acceptance criteria or a QA checklist.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/clawpod-app/awesome-openclaw-agent-packs/test-plan
Install

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.

Any agent
npx skills add clawpod-app/awesome-openclaw-agent-packs --skill test-plan
Clone the repo
git clone --depth 1 https://github.com/clawpod-app/awesome-openclaw-agent-packs

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for test-plan

README.md
[![agentmods](https://agentmods.dev/badge/skills/clawpod-app/awesome-openclaw-agent-packs/test-plan/github.svg)](https://agentmods.dev/skills/clawpod-app/awesome-openclaw-agent-packs/test-plan)
Your own site
<a href="https://agentmods.dev/skills/clawpod-app/awesome-openclaw-agent-packs/test-plan"><img src="https://agentmods.dev/badge/skills/clawpod-app/awesome-openclaw-agent-packs/test-plan/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.

agentmods 80×15 button for test-plan

Your own site · 80×15
<a href="https://agentmods.dev/skills/clawpod-app/awesome-openclaw-agent-packs/test-plan"><img src="https://agentmods.dev/badge/skills/clawpod-app/awesome-openclaw-agent-packs/test-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 47 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 372 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00047 $0.00372
Opus 5 $0.00023 $0.00186
Sonnet 5 $0.00009 $0.00074
Haiku 4.5 $0.00005 $0.00037

Measured 9d ago against content hash 6400aa543716, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

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 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.

packs/qa/skills/test-plan/SKILL.md · 52 lines

The source is not reproduced here

A licence we could not identify

The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.

Read it on GitHub

Changes

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.

  1. 9d ago First seen · 52 lines · 47 tokens per session scan A 6400aa543716

Subscribe to this mod's changes

test-plan is a skill published in the GitHub repository clawpod-app/awesome-openclaw-agent-packs (45 stars, last pushed 5mo ago), with no licence file. It adds 47 tokens to every session and 372 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.

Related

Other skills, from other repositories

verification-engine

Use when verifying build/test/lint before commit, PR, or completion claims. Runs verification pipeline in fresh subagent context with auto-repair. Triggers on /handoff-verify, pre-commit check, build verification, test validation.

sangrokjung/claude-forge · 52 tokens

verify-implementation

A workflow that runs a project’s verification skills to produce a report on coding patterns, architecture rules, and project conventions. It is intended for work after implementation, before a pull request, or during code review.

sangrokjung/claude-forge · 37 tokens

test-first

Use when implementing any feature, bugfix, or refactor that has a testable outcome. Activate for keywords like "TDD", "test-first", "red-green", "write the test first", "implement ", "fix ". Enforces the red-green-refactor discipline -- write a failing test, make it pass with the smallest change, refactor with tests…

duthaho/claudekit · 106 tokens

eval-harness

Formal evaluation framework for Claude Code sessions implementing eval-driven development (EDD) principles.

sangrokjung/claude-forge · 19 tokens

dependency-upgrade

Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing. Use when upgrading framework versions, updating major dependencies, or managing breaking changes in libraries.

sangrokjung/claude-forge · 37 tokens

api-tester

Test HTTP APIs, validate responses, generate test suites, and diagnose API issues.

profclaw/profclaw · 19 tokens