What is create-tests?

A development aid that creates a test plan and individual test cases from requirements and acceptance criteria. It includes normal cases, edge cases, and failure scenarios.

Use it to plan unit, integration, or other relevant tests for a feature, including state changes, analytics events, metrics, logs, and traces when those specifications exist.

It helps turn written requirements into concrete checks, so important behaviours are less likely to go untested.

create-tests — Skill for Claude Code by tomzx

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 tomzx/agents --skill create-tests

Clone the repo

git clone --depth 1 https://github.com/tomzx/agents

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/tomzx/agents/create-tests.svg)](https://agentmods.dev/skills/tomzx/agents/create-tests)

Your own site

<a href="https://agentmods.dev/skills/tomzx/agents/create-tests"><img src="https://agentmods.dev/badge/skills/tomzx/agents/create-tests.svg" alt="Measured on agentmods" height="20"></a>

Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,017 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 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.

Model	Per session	Once invoked
Fable 5.1	$0.00021	$0.01017
Opus 5	$0.00010	$0.00508
Sonnet 5	$0.00004	$0.00203
Haiku 4.5	$0.00002	$0.00102

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

Security

Grade A, and why

create-tests 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 4d 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.

skills/create-tests/SKILL.md · 84 lines

How it starts

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

Create Tests

Produces a test plan with structured test cases derived from requirements, acceptance criteria, and a specification. Covers happy paths, edge cases, and failure scenarios across relevant test levels.

Prerequisites

Apply the shared SDLC conventions in skills/sdlc/references/shared.md.
If no argument is provided, locate the feature directory under .sdlc/features/ whose frontmatter issue field references $ISSUE_NUMBER.
.sdlc/features/N-<slug>/requirements.md and .sdlc/features/N-<slug>/specification.md (both must have passed review with findings verdict approved), or documents provided in context or as a file path ($1)
.sdlc/features/N-<slug>/lifecycle.md (optional, if a lifecycle document was produced): include test cases that verify state transitions, guard conditions, invariants, and retention policies
.sdlc/features/N-<slug>/telemetry.md (optional, if a telemetry plan was produced): include test cases that verify analytics events are emitted correctly
.sdlc/features/N-<slug>/observability.md (optional, if an observability plan was produced): include test cases that verify metrics, logs, and traces are emitted correctly
Information about the testing stack (if available)

Steps

Read the requirements, specification, lifecycle document, telemetry plan, and observability plan (if present).
List all acceptance criteria that need to be verified. In requirements.md these are the fenced gherkin scenarios, each tagged with its requirement ID (@FR-N / @NFR-N); map test cases to scenarios via that tag.
For each acceptance criterion, write at least one test case. When the project uses a BDD framework (pytest-bdd, cucumber), a gherkin scenario can be executed directly; otherwise translate the scenario's Given/When/Then into the test case's Setup/Steps/Expected.
For each analytics event in the telemetry plan, write a test case verifying the event is emitted with correct properties.
For each metric, log entry, and trace span in the observability plan, write a test case verifying it is emitted correctly.
Add edge case and failure scenario tests beyond the acceptance criteria.
Organize test cases by test level (unit, integration, end-to-end).
Identify test infrastructure and fixtures needed.
Write the output to .sdlc/features/N-<slug>/tests.md.

Read the full file on GitHub · 84 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.

4d ago First seen · 84 lines · 21 tokens per session scan A 3d81fcb03b03

Subscribe to this mod's changes

create-tests is a skill published in the GitHub repository tomzx/agents (6 stars, last pushed 4d ago), licensed MIT. It adds 21 tokens to every session and 1,017 once invoked, about $0.0001 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.

Testing

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

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

neuron-evaluation-engineer

Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…

neuron-core/neuron-ai · 77 tokens

create-tests