A quality-assurance guide for designing and running feature tests from requirements. It covers BDD, a way to describe behavior in Given/When/Then steps, plus exploratory testing and bug reproduction.

Use it to design test cases, write BDD specifications, validate completed features, review end-to-end tests, perform exploratory testing, and create QA reports.

It turns acceptance criteria into concrete checks and records whether the feature behaves as requested. This helps reveal missing scenarios and provides clear evidence for failures.

tester — Skill for Claude Code by olehsvyrydov/AI-development-team

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 olehsvyrydov/AI-development-team --skill tester

Clone the repo

git clone --depth 1 https://github.com/olehsvyrydov/AI-development-team

Made for: Claude Code.

Or install ai-dev-team, the plugin that ships this one along with the rest of its 43 skills, 50 commands.

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/olehsvyrydov/ai-development-team/tester/github.svg)](https://agentmods.dev/skills/olehsvyrydov/ai-development-team/tester)

Your own site

<a href="https://agentmods.dev/skills/olehsvyrydov/ai-development-team/tester"><img src="https://agentmods.dev/badge/skills/olehsvyrydov/ai-development-team/tester/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/olehsvyrydov/ai-development-team/tester"><img src="https://agentmods.dev/badge/skills/olehsvyrydov/ai-development-team/tester.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 4,925 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.00069	$0.04925
Opus 5.5	$0.00028	$0.01970
Sonnet 5.5	$0.00014	$0.00985
Haiku 4.5	$0.00007	$0.00492

Measured today against content hash ebd9eb908c36, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

tester 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 today.

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/quality/testing/tester/SKILL.md · 437 lines

How it starts

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

Test Case Designer & QA (/qa)

Gate Check (workflow)

Consult the workflow-engine skill first. /qa runs after CODE_REVIEWED is passed.

Before: refuse to start formal testing until CODE_REVIEWED is set (hand back to /rev if not).
On completion: record the outcome to the ledger as qa: { outcome, by, at, evidence } (the canonical structure /verify reads before setting VERIFIED — see workflow-engine/references/ledger.md). On failure, return the ticket to the Dev/Implementation stage for the developer to address, listing the failing scenarios. Final sign-off is /verify's VERIFIED gate.

Trigger

Use this skill when:

User invokes /qa, /rob, or /tester command
User asks for "Rob" by name for QA testing
Designing test cases from acceptance criteria
Writing BDD specs (Given/When/Then) from behavioral AC
Reviewing /e2e tests against approved test cases
Testing features against acceptance criteria
Validating implemented features work as specified
Creating QA test reports
Performing exploratory testing
Black-box testing of features
Writing reproduction tests for bugs

Context

You are /qa (alias: Rob), a Senior QA Engineer with 10+ years of experience in test case design and black-box testing. You design test cases from behavioral acceptance criteria, write BDD specs, review /e2e automated tests against approved test cases, and test features from the end-user perspective. You validate that implementations meet acceptance criteria. You do NOT write unit or integration tests (developers do that). You focus on test design, feature validation, user experience, and finding defects before release.

Documentation Lookup (MANDATORY)

Before testing features, check the latest documentation to understand expected behavior:

Context7 MCP

Use Context7 MCP to retrieve up-to-date documentation for any library or framework:

Resolve library: Call mcp__context7__resolve-library-id with the library name
Query docs: Call mcp__context7__query-docs with the resolved library ID and your question

Read the full file on GitHub · 437 lines

Files

What ships with it

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

today First seen · 437 lines · 69 tokens per session scan A ebd9eb908c36

Subscribe to this mod's changes

tester is a skill published in the GitHub repository olehsvyrydov/AI-development-team (17 stars, last pushed today), licensed MIT. It adds 69 tokens to every session and 4,925 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-10-19.

E2E testing Testing agentic-workflow ai-agents ai-dev-tools anthropic

product-verification

Drive the running product and verify it works end-to-end. Use this skill after a deploy, before a release, or when the user says "verify", "smoke test", "does it work", "test the flow", "check staging", "end-to-end test", or "drive the product". Also use when the user wants to verify a specific user journey (signup…

rbah31/claude-code-workflow · 112 tokens

tdd-workflow

Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.

affaan-m/ECC · 43 tokens

verify

Verify that a code change actually does what it's supposed to by exercising it end-to-end and observing behavior — drive the affected flow, not just tests or typecheck. Run before committing nontrivial changes; bootstraps this repo's project verify skill if none exists yet. Don't invoke it on a diff that only touches…

asgeirtj/system_prompts_leaks · 95 tokens

tester