create-test-plan

create-test-plan is a skill for Claude Code from tobihagemann/turbo. It costs 56 tokens per session (2,010 once invoked), scanned A, original, MIT.

A structured test-plan generator for recent code changes. It writes a Markdown file covering basic behavior, complex operations, adversarial tests, and scenarios that cross different parts of the system.

In plain words
What is it for?
Use it to answer what should be tested, plan tests, or generate test scenarios. The plan is saved under `.turbo/test-plans/`.
Why use it?
It turns a change or feature into a clear list of checks, so important cases are less likely to be missed. It can use a specified scope, pull request, recent conversation, or project discovery.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: names the AskUserQuestion tool.

Part of the turbo plugin — 71 skills shipped together

Good fit Use it to answer what should be tested, plan tests, or generate test scenarios. The plan is saved under .turbo/test-plans/.

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

Made for: Claude Code.

Or install turbo, the plugin that ships this one along with the rest of its 71 skills.

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

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/tobihagemann/turbo/create-test-plan"><img src="https://agentmods.dev/badge/skills/tobihagemann/turbo/create-test-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,010 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original 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.00056 $0.02010
Opus 5.5 $0.00022 $0.00804
Sonnet 5.5 $0.00011 $0.00402
Haiku 4.5 $0.00006 $0.00201

Measured 3d ago against content hash 905c63960e29, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

create-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 3d 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.

claude/skills/create-test-plan/SKILL.md · 154 lines

How it starts

The opening of the file, as written. The whole thing — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Create Test Plan

Analyze what changed and generate a comprehensive test plan covering four escalating levels of testing depth.

Step 1: Determine Scope

Resolve scope using the first match:

  1. User-specified — the user says what to test. Use that.
  2. PR — a PR URL or number is provided. Fetch the PR details (title, description, changed files, comments) and read the changed code.
  3. Conversation context — prior conversation contains recent work (a feature, fix, or refactor). Extract what changed, where it lives, and expected behavior.
  4. App-level discovery — fresh context with no prior work. Examine the project (entry points, routes, commands, README) to identify the app's core user-facing flows.

If the resolved scope spans more than one git branch and the user named no single branch, cover each of them instead of only the branch currently checked out. Include scenarios that exercise them together where the branches can be combined in the working tree the plan's executor will have, and state the required branch state in each such scenario's steps.

Step 2: Determine Testing Approach

Always check for project-specific testing skills or MCP tools first. Use the fallbacks below when nothing project-specific is available:

  • Web app → /agent-browser skill if available, otherwise claude-in-chrome MCP
  • UI/native app → computer-use MCP
  • CLI tool → direct terminal execution
  • Library with no entry point → report that interactive testing is not applicable and stop, unless the scope changes a check's configuration; then use direct terminal execution for that part of the scope

Step 3: Resolve the Output Path

Pick a slug for the test plan from the change under test:

  • Lowercase
  • Replace non-alphanumeric characters with hyphens
  • Collapse consecutive hyphens
  • Trim leading and trailing hyphens
  • Truncate to 40 characters at a word boundary

If the work is anchored to an existing plan at .turbo/plans/<slug>.md, reuse that plan's slug verbatim.

Read the full file on GitHub · 154 lines

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. 3d ago Changed · -31 tokens per session 905c63960e29
  2. 27d ago Changed · +2 lines ad6f4a2e12f7
  3. 1mo ago Changed · +2 lines 46ac613f92a0
  4. 2mo ago Changed 6ee388d4d304
  5. 2mo ago Changed · +2 lines 1d4974631bc2
  6. 2mo ago Changed · +2 lines 475cb23a7078
  7. 2mo ago First seen · 146 lines · 87 tokens per session scan A a7edddfe7fa4

Subscribe to this mod's changes

create-test-plan is a skill published in the GitHub repository tobihagemann/turbo (420 stars, last pushed today), licensed MIT. It adds 56 tokens to every session and 2,010 once invoked, about $0.0002 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-08-30.

Related

create-test-plan compared with skills from other repositories

create-test-plan next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
create-test-plantobihagemann/turboSkill420todayMITA56Claude Code
offensive-c2-frameworksSnailSploit/Claude-RedSkill11kyesterdayMITA250Claude Code, Codex
offensive-crypto-attacksSnailSploit/Claude-RedSkill11kyesterdayMITA261Claude Code, Codex
offensive-parameter-pollutionSnailSploit/Claude-RedSkill11kyesterdayMITA0Claude Code, Codex
offensive-z-waveSnailSploit/Claude-RedSkill11kyesterdayMITA113Claude Code, Codex
fiscalisteromainsimon/paperasseSkill2.6ktodayMITA306Claude Code
comptableromainsimon/paperasseSkill2.6ktodayMITA248Claude Code