What is create-agent-tests?

A tool for writing and running tests as Markdown case files that a coding agent follows against a live environment. The result is an auditable report marked PASS, FAIL, BLOCKED, or ABORTED, with collected evidence.

It is for testing user interfaces, APIs, databases, full-stack workflows, browser behaviour, logs, files, network activity, cloud state, and telemetry.

It fits checks that need judgment across several systems, where fixed tests would be brittle, premature, too costly, or too narrow.

create-agent-tests — Skill for Claude Code and Codex by ShiplightAI

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 ShiplightAI/agent-skills --skill create-agent-tests

Clone the repo

git clone --depth 1 https://github.com/ShiplightAI/agent-skills

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/shiplightai/agent-skills/create-agent-tests/github.svg)](https://agentmods.dev/skills/shiplightai/agent-skills/create-agent-tests)

Your own site

<a href="https://agentmods.dev/skills/shiplightai/agent-skills/create-agent-tests"><img src="https://agentmods.dev/badge/skills/shiplightai/agent-skills/create-agent-tests/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/shiplightai/agent-skills/create-agent-tests"><img src="https://agentmods.dev/badge/skills/shiplightai/agent-skills/create-agent-tests.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 1,477 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.00070	$0.01477
Opus 5.5	$0.00028	$0.00591
Sonnet 5.5	$0.00014	$0.00295
Haiku 4.5	$0.00007	$0.00148

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

Security

Grade A, and why

create-agent-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 2mo ago.

The scan reads SKILL.md. This mod also ships 1 executable file (assets/run-agent-verification.ts), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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-agent-tests/SKILL.md · 153 lines

How it starts

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

Agent Tests

Producer skill for agent tests: a coding agent executes a Markdown case file against a target environment and returns an auditable report. Verification is the executing agent's judgment plus the evidence it collects (browser, API, DB, logs, cloud, telemetry), rather than fixed deterministic assertions.

This skill authors and runs agent tests. Each case produces an auditable report — a report path, a final PASS/FAIL/BLOCKED/ABORTED status, and the collected evidence artifacts — for whatever invoked it to consume.

When To Use Agent Tests

Use agent tests when verification requires flexible, tool-driven judgment across UI, API, database, logs, files, network, or live-environment state, and a deterministic test would be premature, brittle, too expensive, or too narrow.

Especially useful for:

UI changes needing visual, interactive, browser-console, network, or trace verification.
API and DB workflows where confidence requires live requests plus persisted state inspection.
Full-stack flows crossing frontend, backend, storage, jobs, external mocks, and cleanup.
Exploratory regression checks before converting a stable path into a standard unit, contract, integration, YAML E2E, or other deterministic test.

Agent tests are not a replacement for deterministic tests. Prefer converting high-value stable agent flows into a standard deterministic test (unit, contract, integration, YAML E2E, or other) once the path stabilizes.

Project Layout

Agent tests live under tests/agent/ in the target repo:

tests/agent/agent-test-suites.json   suite manifest (project-owned)
tests/agent/<feature>/<case>.md       case files, one logical journey each
tests/agent/run-agent-verification.ts runner/orchestrator
agent-test-reports/                    generated reports; do not hand-edit

The repo owns its real agent-test-suites.json, case files, fixture setup, auth/session bootstrap, CI wiring, engine secrets and MCP config, staging/production mutation policies, and cleanup ownership.

Read the full file on GitHub · 153 lines

Files

What ships with it

4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

2mo ago First seen · 153 lines · 70 tokens per session scan A 28d73346aa3b

Subscribe to this mod's changes

create-agent-tests is a skill published in the GitHub repository ShiplightAI/agent-skills (2 stars, last pushed 3mo ago), licensed MIT. It adds 70 tokens to every session and 1,477 once invoked, about $0.0003 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-31.

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

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

create-agent-tests