A test-case generator for Jira tickets and their acceptance criteria. It produces Playwright browser-test scenarios, a short developer unit-test checklist, and a mapping from requirements to tests.

Creating browser-test starting points, listing unit tests for developers, tracing tests back to acceptance criteria, and checking an Epic test plan before writing scenarios.

It turns ticket requirements into concrete checks while avoiding duplicate coverage. It also shows which requirements are tested and follows the project's existing test style.

test-cases — Skill for Claude Code and Codex by TimothyHan

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 TimothyHan/qa-buddy-skills --skill test-cases

Clone the repo

git clone --depth 1 https://github.com/TimothyHan/qa-buddy-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/timothyhan/qa-buddy-skills/test-cases/github.svg)](https://agentmods.dev/skills/timothyhan/qa-buddy-skills/test-cases)

Your own site

<a href="https://agentmods.dev/skills/timothyhan/qa-buddy-skills/test-cases"><img src="https://agentmods.dev/badge/skills/timothyhan/qa-buddy-skills/test-cases/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/timothyhan/qa-buddy-skills/test-cases"><img src="https://agentmods.dev/badge/skills/timothyhan/qa-buddy-skills/test-cases.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 2,515 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.

Model	Per session	Once invoked
Fable 5.1	$0.00119	$0.02515
Opus 5	$0.00060	$0.01257
Sonnet 5	$0.00024	$0.00503
Haiku 4.5	$0.00012	$0.00251

Measured yesterday against content hash 2fbf440f1641, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

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.

The scan reads SKILL.md. This mod also ships 1 executable file (tests/cases/projects-happy/input/playwright/tests/smoke.spec.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.

core/skills/test-cases/SKILL.md · 221 lines

How it starts

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

/qa-test-cases: Generate Test Cases from ACs

You are an SDT partner generating test cases for a ticket. You pull the ticket's ACs from Jira, cross-reference the epic test plan, and produce:

E2E test scenarios (steps and expected results — /qa-e2e-write implements them)
Unit test checklist (for developers)
Requirements-to-test mapping (for traceability)

Constraints

Match the project's test style. Read existing Playwright tests first. Use the same patterns, imports, helpers, page objects.
No implementation code in test cases. Steps and expected results are the contract; /qa-e2e-write owns selectors, waits and fixtures. Put automation constraints a writer must know (isolation, run-once, data hygiene) into Preconditions.
Every test case traces to a requirement. No orphan tests. No untested ACs.
Unit test checklist is for devs. Keep it brief and actionable — describe what to test, not how.
Don't duplicate existing tests. If a scenario is already covered, reference it instead of creating a new one.
Prioritize ruthlessly. A ticket with 3 ACs doesn't need 30 test cases. Focus on what catches real bugs.
Observed beats assumed. A precondition or step that names a control label, a seeded record, a displayed value or a request the browser makes comes from the running app (Phase 1 step 8) or carries (unverified) for /qa-e2e-pom to settle. Never assert the network behaviour of a page you have not watched.

Scratchpad (run protocol): write ## Plan to the run's scratchpad.md before Phase 1; at each phase boundary and every Review Options pause update ## State and re-read the scratchpad before continuing; drop noteworthy things into ## Candidate learnings as you go.

Phase 1: Gather Context

Input: User provides a ticket key (e.g., PROJ-789) or pastes ticket details.

Read .qabuddy.json (if exists) for context source and team mode.
- contextSource: "spec" → search workspace for spec files before asking
- contextSource: "chat" → skip Jira, ask SDT for context directly
- contextSource: "jira" or no config → current behavior

Read the full file on GitHub · 221 lines

Files

What ships with it

60 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.

yesterday Changed · +6 lines 2fbf440f1641
2d ago Changed 8525dc43f670
4d ago Changed · +9 lines f2417f72c553
5d ago Changed · -18 lines · +8 tokens per session 4448e8eec5d8
9d ago First seen · 224 lines · 111 tokens per session scan A 985d73ff9034

Subscribe to this mod's changes

test-cases is a skill published in the GitHub repository TimothyHan/qa-buddy-skills (8 stars, last pushed yesterday), licensed Apache-2.0. It adds 119 tokens to every session and 2,515 once invoked, about $0.0006 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-08-31.

Claude Code E2E testing Testing Unit testing agent-memory ai-agents context-engineering playwright qa

gsd-add-tests

Generate tests for a completed phase based on UAT criteria and implementation.

open-gsd/gsd-core · 18 tokens

06-test

Write and iterate tests until they pass, or validate a user journey end to end in the browser. Use when the user wants to add coverage, find what's untested, or walk a flow. Not for auditing test health or debugging a failure.

ai-driven-dev/framework · 52 tokens

qawolf-cli

Manage QA Wolf through the qawolf CLI. Use when asked to create, update, or list coverage requests, bug reports, or maintenance reports; start a run of flows or tags on the QA Wolf platform or read a run's results; list, set, or delete environment variables; manage environments, flows, or tags; request automation of…

qawolf/cli · 118 tokens

test-writer

Write tests with TDD following structured patterns. Ensures consistent AAA structure, proper coverage targets, and framework-specific conventions. Without this skill, tests lack consistent naming, miss coverage targets, and skip anti-pattern checks.

nguyenthienthanh/aura-frog · 47 tokens

test-review

A review checklist for newly written or changed automated tests using TypeScript and Playwright. Playwright is a tool for testing web browsers, and automated tests check software without repeating the steps by hand.

akovalion/paranoid-qa · 119 tokens

playwright-expert

Expert in Playwright E2E testing framework, auto-waiting mechanisms, test generation, trace viewer, and CI/CD integration. Use when the user mentions testing, end-to-end tests, QA, automation, end-to-end testing, or test automation, or when the task involves Playwright Framework, Test Organization, Advanced Features…

personamanagmentlayer/pcl · 77 tokens