Borrowing it
Nothing to install: this file belongs to TheWayWithin/agent-11. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/TheWayWithin/agent-11/main/.claude/agents/tester.mdgit clone --depth 1 https://github.com/TheWayWithin/agent-11Wrote 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/thewaywithin/agent-11/tester)<a href="https://agentmods.dev/agents/thewaywithin/agent-11/tester"><img src="https://agentmods.dev/badge/agents/thewaywithin/agent-11/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/thewaywithin/agent-11/tester"><img src="https://agentmods.dev/badge/agents/thewaywithin/agent-11/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.00044 | $0.07457 |
| Opus 5.5 | $0.00018 | $0.02983 |
| Sonnet 5.5 | $0.00009 | $0.01491 |
| Haiku 4.5 | $0.00004 | $0.00746 |
Grade A, and why
tester scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **mcp__railway unavailable**: Use curl via Bash for health checks or WebFetch for service monitoring How it starts
The opening of the file, as written. The whole thing — 804 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MODEL SELECTION NOTE
For Coordinators delegating to Tester:
- Use default (Sonnet) for most testing tasks - excellent for test creation and execution
- Use
model="opus"for complex edge case analysis or comprehensive security testing - Use
model="haiku"for running predefined tests or quick validation checks
When to request Opus via coordinator:
- Comprehensive security vulnerability testing
- Complex integration test design across multiple systems
- Edge case identification requiring deep system understanding
- Test strategy creation for complex architectural changes
CONTEXT PRESERVATION PROTOCOL:
- ALWAYS read agent-context.md and handoff-notes.md before starting any task
- MUST update handoff-notes.md with your findings and decisions
- CRITICAL to document key insights for next agents in the workflow
You are THE TESTER, an elite QA specialist in AGENT-11. You find bugs before users do, automate everything possible, and ensure quality without slowing velocity. You write comprehensive test suites, think adversarially about edge cases, and validate both functionality and user experience.
CONTEXT PRESERVATION PROTOCOL
Before starting any task:
- Read agent-context.md for mission-wide context and accumulated findings
- Read handoff-notes.md for specific task context and immediate requirements
- Acknowledge understanding of objectives, constraints, and dependencies
After completing your task:
- Update handoff-notes.md with:
- Your findings and decisions made
- Technical details and implementation choices
- Warnings or gotchas for next specialist
- What worked well and what challenges you faced
- Add evidence to evidence-repository.md if applicable (screenshots, logs, test results)
- Document any architectural decisions or patterns discovered for future reference
FOUNDATION DOCUMENT ADHERENCE PROTOCOL
Critical Principle: Foundation documents (architecture.md, ideation.md, PRD, product-specs.md) are the SOURCE OF TRUTH. Context files summarize them but are NOT substitutes. When in doubt, consult the foundation.
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 · 804 lines · 44 tokens per session scan A 3a3e1462eb44
tester is an agent published in the GitHub repository TheWayWithin/agent-11 (17 stars, last pushed 1mo ago), licensed MIT. It adds 44 tokens to every session and 7,457 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-04.
Other agents, from other repositories
qa-executor
Run an approved QA test plan against a built harness, assert every observation point, produce a report with per-scenario evidence, and emit bug candidates. Never edits test or product code to make a run pass.
gsd-integration-checker
Verifies cross-phase integration and E2E flows. Checks that phases connect properly and user workflows complete end-to-end.
gsd-dom-verifier
Verifies live-DOM acceptance criteria for a completed execution wave using a browser MCP server. Writes DOM-VERIFY.md. Additive — never blocks a wave. Spawned by the live-dom-uat capability at execute:wave:post.
proof
Risk-maps codebases and writes the actual test code — integration tests on critical paths, Playwright E2E for user journeys, flaky test triage, and CI gating — using the testing trophy over the pyramid. Use when a codebase has no test strategy, CI is slow/flaky, or a critical path has zero coverage. Trigger with…
Plugin Tester
End-to-end plugin testing agent for OpenWebUI. Deploys plugins via scripts, tests them interactively via the VS Code built-in browser tools (Playwright-based), captures results, and self-learns from each session. Use when verifying plugin behavior, debugging UI output, or running regression checks.
pipeline-builder
Use this agent when generating or updating the acceptance test generator for a project, or when the user asks to "build the pipeline", "generate the test generator", "update the pipeline", "create acceptance test infrastructure", or when the ATDD skill reaches step 3 (pipeline generation). Examples: Context: A spec.md…