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.
npx agentmods add commands/latestaiagents/agent-skills/write-test-casesgit clone --depth 1 https://github.com/latestaiagents/agent-skillsWrote 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.
[](https://agentmods.dev/commands/latestaiagents/agent-skills/write-test-cases)<a href="https://agentmods.dev/commands/latestaiagents/agent-skills/write-test-cases"><img src="https://agentmods.dev/badge/commands/latestaiagents/agent-skills/write-test-cases.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00009 | $0.00300 |
| Opus 5 | $0.00005 | $0.00150 |
| Sonnet 5 | $0.00002 | $0.00060 |
| Haiku 4.5 | $0.00001 | $0.00030 |
Grade A, and why
write-test-cases 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 yesterday.
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.
What it actually says
/write-test-cases
Generate comprehensive test cases for a feature or user story.
What I Need
Tell me:
- Feature or user story to test
- Type of testing (functional, regression, E2E)
- Format preference (table, BDD/Gherkin, standard)
- Priority focus (smoke, full coverage)
What I'll Create
Comprehensive test cases covering:
- Happy path - Normal successful flows
- Negative cases - Error handling, validation
- Edge cases - Boundary values, limits
- Security - Input validation, auth checks
- Performance - Load considerations
Output Formats
Table Format
| ID | Title | Steps | Expected |
BDD/Gherkin
Feature: ...
Scenario: ...
Given/When/Then
Standard
Preconditions, Steps, Expected, Postconditions
Example
You: /write-test-cases
Feature: User registration with email verification
Format: BDD
Claude: [Generates comprehensive Gherkin scenarios covering
happy path, validation errors, duplicate email, expired links,
resend verification, etc.]
Techniques Applied
- Equivalence partitioning
- Boundary value analysis
- Decision tables
- State transitions
- Error guessing
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.
- yesterday First seen · 66 lines · 9 tokens per session scan A fd68f017e3b5
write-test-cases is a command published in the GitHub repository latestaiagents/agent-skills (5 stars, last pushed 4mo ago), licensed MIT. It adds 9 tokens to every session and 300 once invoked, about $0.0000 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.
Other commands, from other repositories
test-feature
Test a React Native feature on the running simulator/emulator. Verifies UI, user flows, and internal state. Generates a persistent Maestro test file.
fdk-react-create
Create a new Platform 3.0 React Meta app (default UI stack). Uses fdk create react-starter-template or react-meta skeletons with DEW components, metaConfig in manifest.json, and React Router.
run-workflow
Validate and establish the proven rn-dev-agent operating sequence before a real React Native journey — declared package manager and dependencies, read-only inventory, typed session recovery, one exclusive device, managed integration and Metro, only the requested proof, reverse-order cleanup.
fdk-refactor
Reduce function complexity in a Freshworks app to meet cyclomatic complexity ≤ 7 per function. Extracts helper functions, simplifies conditionals, and preserves behavior while improving code quality.
build-and-test
Build the Expo/React Native app (local or EAS), install on simulator/emulator, start Metro, then test the specified feature end-to-end.
fw-setup-uninstall
Uninstall FDK completely — keeps Node.js and nvm (/fw-setup uninstall).