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.
git clone --depth 1 https://github.com/davidmatousek/agentic-oriented-development-kitWrote 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/agents/davidmatousek/agentic-oriented-development-kit/tester)<a href="https://agentmods.dev/agents/davidmatousek/agentic-oriented-development-kit/tester"><img src="https://agentmods.dev/badge/agents/davidmatousek/agentic-oriented-development-kit/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.
<a href="https://agentmods.dev/agents/davidmatousek/agentic-oriented-development-kit/tester"><img src="https://agentmods.dev/badge/agents/davidmatousek/agentic-oriented-development-kit/tester.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00110 | $0.02768 |
| Opus 5.5 | $0.00044 | $0.01107 |
| Sonnet 5.5 | $0.00022 | $0.00554 |
| Haiku 4.5 | $0.00011 | $0.00277 |
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 1mo ago.
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.
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.
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.mdfor 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 @prioritytags - Run Tests: Execute with
npm run test:batch3or tag filters - Document: Update
tests/README.mdwith coverage changes
Bug Handling
When tests fail unexpectedly:
- Document failing scenario and observed vs expected behavior
- Invoke
debuggeragent 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)
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.
- 1mo ago First seen · 259 lines · 110 tokens per session scan A 7c3fd93160e7
tester is an agent published in the GitHub repository davidmatousek/agentic-oriented-development-kit (24 stars, last pushed 3mo ago), licensed MIT. It adds 110 tokens to every session and 2,768 once invoked, about $0.0004 per session on Opus 5.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.
Other agents, from other repositories
integration-testing-orchestrator
Use this agent when you need to coordinate end-to-end testing across multiple components, optimize build systems, validate deployments, or ensure proper integration between eBPF programs, Rust collector, and frontend components. Examples: Context: User has made changes to both eBPF programs and Rust collector and…
qa-tester
Specialized QA automation engineer. Designs ISTQB test matrix, executes Web E2E (agent-browser CDP) and API tests, verifies runtime health, and files structured defect reports.
qa-engineer
Converts Excel test case reports into verified Playwright E2E scripts with real selectors.
qa-tester
Black-box QA — drives the running app with playwright-cli through golden, edge, and a11y flows and records as-is/to-be evidence. Distinct from Verify, which re-runs the real tests with no browser.
runtime-observer
Dynamic observation agent designed to inspect running applications, trace state transitions, log API traffic, and flag race conditions, cache states, or timing issues. Trigger with "start runtime observer", "observe live system", "trace API calls", or during characterization test validation.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.