write-test-plan

write-test-plan is a skill for Claude Code from yebot/rad-cc-plugins. It costs 8 tokens per session (2,202 once invoked), scanned A, original, no licence file.

A document that describes how a feature or change should be tested.

In plain words
What is it for?
Planning tests for new features, updates, and other software changes.
Why use it?
It helps teams cover expected behavior and possible failure cases before or during implementation.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter.

Part of the webapp-team plugin — 7 skills, 8 commands, 11 agents shipped together

Good fit Planning tests for new features, updates, and other software changes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/yebot/rad-cc-plugins/write-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 yebot/rad-cc-plugins --skill write-test-plan
Clone the repo
git clone --depth 1 https://github.com/yebot/rad-cc-plugins

Made for: Claude Code.

Or install webapp-team, the plugin that ships this one along with the rest of its 7 skills, 8 commands, 11 agents.

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 write-test-plan

README.md
[![agentmods](https://agentmods.dev/badge/skills/yebot/rad-cc-plugins/write-test-plan/github.svg)](https://agentmods.dev/skills/yebot/rad-cc-plugins/write-test-plan)
Your own site
<a href="https://agentmods.dev/skills/yebot/rad-cc-plugins/write-test-plan"><img src="https://agentmods.dev/badge/skills/yebot/rad-cc-plugins/write-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 write-test-plan

Your own site · 80×15
<a href="https://agentmods.dev/skills/yebot/rad-cc-plugins/write-test-plan"><img src="https://agentmods.dev/badge/skills/yebot/rad-cc-plugins/write-test-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 8 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,202 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.00008 $0.02202
Opus 5.5 $0.00003 $0.00881
Sonnet 5.5 $0.00002 $0.00440
Haiku 4.5 $0.00001 $0.00220

Measured 1mo ago against content hash 910a3bf33c72, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

write-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 1mo 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.

plugins/webapp-team/skills/write-test-plan/SKILL.md · 374 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

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. 1mo ago First seen · 374 lines · 8 tokens per session scan A 910a3bf33c72

Subscribe to this mod's changes

write-test-plan is a skill published in the GitHub repository yebot/rad-cc-plugins (9 stars, last pushed 10mo ago), with no licence file. It adds 8 tokens to every session and 2,202 once invoked, about $0.0000 per session on Opus 5.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

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

eval-dataset-design

A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.

bojieli/ai-agent-book · 138 tokens

tika-eval-compare

Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".

apache/tika · 50 tokens

cua-driver

Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.

davidondrej/skills · 68 tokens

jetson-validate-image

Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.

NVIDIA/skills · 50 tokens

atmos-validation

Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.

cloudposse/atmos · 31 tokens