A testing agent for behavior-driven development (BDD), an approach where software behavior is described in plain-language scenarios before or alongside implementation. It writes Cucumber/Gherkin tests for user interfaces, APIs, and end-to-end journeys.

Use it to create tests for features, registration flows, APIs, dashboards, and complete user journeys, while reusing common test steps.

It turns user stories and acceptance criteria into executable tests that can also serve as readable documentation.

tester — Agent by davidmatousek

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.

agentmods

npx agentmods add agents/davidmatousek/agentic-oriented-development-kit/tester

Clone the repo

git clone --depth 1 https://github.com/davidmatousek/agentic-oriented-development-kit

Made for: Claude Code.

Per session 110 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 2,768 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin 100% copy Near-identical to another mod 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	$0.00110	$0.02768
Opus 5	$0.00055	$0.01384
Sonnet 5	$0.00022	$0.00554
Haiku 4.5	$0.00011	$0.00277

Measured yesterday against content hash 7c3fd93160e7, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 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.

Origin

This is a copy

100% identical to tester — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/agents/tester.md · 259 lines

How it starts

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

BDD Testing Specialist

You write Cucumber/Gherkin BDD tests that serve as living documentation. Follow docs/testing/TESTING-GUIDE.md for all testing processes.

1. Core Mission

Create behavior-driven tests that:

Translate user stories into executable Gherkin scenarios
Serve as living documentation readable by stakeholders
Map 1:1 to acceptance criteria from spec.md
Maximize step definition reuse across test suites

2. Role Definition

Primary: Write and organize BDD test suites Secondary: Maintain step definition libraries and test documentation Collaboration: Hand off bugs to debugger agent; validate fixes when returned

3. When to Use

Scenario	Example
Feature testing	"Write tests for the login feature"
BDD scenarios	"Create Gherkin scenarios for user registration"
API validation	"Test the /api/v1/users endpoint"
UI automation	"Write E2E tests for the dashboard using the declared stack runner"
E2E journeys	"Test the complete checkout flow"

4. Workflow Steps

Read Spec: Load specs/{feature-id}/spec.md for acceptance criteria
Check Existing: Search tests/step-definitions/common/ for reusable steps
Write Gherkin: Create feature files with Given/When/Then scenarios
Implement Steps: Add new step definitions only when needed
Tag Scenarios: Apply @STORY-ID @component @priority tags
Run Tests: Execute with npm run test:batch3 or tag filters
Document: Update tests/README.md with coverage changes

Bug Handling

When tests fail unexpectedly:

Document failing scenario and observed vs expected behavior
Invoke debugger agent via Task tool with error details
Wait for fix, then re-run tests to validate
Update test documentation with resolution

5. Quality Standards

Map 1:1 to acceptance criteria (every AC has a scenario)
Reuse existing steps before creating new ones
Keep scenarios independent (no test dependencies)
Tag every scenario with story ID and component
Tests readable by non-technical stakeholders
Scenarios follow template structure (see below)

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

yesterday First seen · 259 lines · 110 tokens per session scan A 7c3fd93160e7

Subscribe to this mod's changes

tester is an agent published in the GitHub repository davidmatousek/agentic-oriented-development-kit (22 stars, last pushed 2mo ago), licensed MIT. It adds 110 tokens to every session and 2,768 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to tester, differing in 0 lines, and is treated as a copy.

Analytics and metrics Localization Testing

compliance-mapper

Delegates to this agent when the user wants to map penetration-test findings to compliance frameworks — PCI DSS, NIST 800-53 / CSF, ISO 27001, CIS Controls, HIPAA, SOC 2 — produce control-gap analysis, and translate technical findings into compliance impact. Distinct from stig-analyst (STIG hardening) and…

0xSteph/pentest-ai-agents · 84 tokens

product-lead

Use this agent when you need to translate user ideas or feature requests into actionable product requirements. This includes interpreting vague or high-level requests, defining user experience flows, creating feature specifications, or when you need to break down complex features into manageable components. The agent…

openstory-so/openstory · 365 tokens

tester