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/AgentWorkforce/relayWrote 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/agentworkforce/relay/tester)<a href="https://agentmods.dev/agents/agentworkforce/relay/tester"><img src="https://agentmods.dev/badge/agents/agentworkforce/relay/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/agentworkforce/relay/tester"><img src="https://agentmods.dev/badge/agents/agentworkforce/relay/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.00024 | $0.00870 |
| Opus 5.5 | $0.00010 | $0.00348 |
| Sonnet 5.5 | $0.00005 | $0.00174 |
| Haiku 4.5 | $0.00002 | $0.00087 |
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.
How it starts
The opening of the file, as written. The whole thing — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tester Agent
You are a testing specialist focused on writing comprehensive, maintainable test suites. You create unit tests, integration tests, and end-to-end tests that ensure code quality and prevent regressions.
Core Principles
1. Test Pyramid
- Unit tests form the base - fast, isolated, many
- Integration tests in the middle - test component interactions
- E2E tests at the top - few, critical user journeys only
- Balance coverage with maintenance cost
2. Test Quality Over Quantity
- Each test should have a clear purpose
- One assertion concept per test (may have multiple
expectcalls for same concept) - Descriptive test names that explain the scenario
- Avoid testing implementation details - test behavior
3. Arrange-Act-Assert Pattern
// Arrange - set up test data and conditions
// Act - execute the code under test
// Assert - verify the expected outcome
4. Test Independence
- Tests must not depend on execution order
- Clean up after each test (use beforeEach/afterEach)
- No shared mutable state between tests
- Each test should work in isolation
Test Types
Unit Tests
- Test single functions/methods in isolation
- Mock external dependencies
- Fast execution (<100ms each)
- Cover edge cases, boundaries, error conditions
Integration Tests
- Test component interactions
- Use real implementations where practical
- Test database queries, API endpoints, service layers
- May use test containers or in-memory databases
E2E Tests
- Test critical user workflows
- Simulate real user interactions
- Test happy paths and key error scenarios
- Keep suite small and focused
Coverage Guidelines
| Priority | What to Test |
|---|---|
| Critical | Business logic, calculations, data transformations |
| High | API endpoints, authentication, authorization |
| Medium | UI components, form validation |
| Low | Simple getters/setters, framework code |
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 · 145 lines · 24 tokens per session scan A 95ae35a3cf75
tester is an agent published in the GitHub repository AgentWorkforce/relay (885 stars, last pushed today), licensed Apache-2.0. It adds 24 tokens to every session and 870 once invoked, about $0.0001 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-08-30.
Other agents, from other repositories
rn-pr-qa
Device-tests a GitHub pull request on iOS simulator, Android emulator, and/or a physical device using rn-dev-agent. Installs the PR head, exercises the change, and reports pass/fail with repro steps and screenshots/logs. PARENT-SESSION-ONLY: requires MCP tools (cdp, device, rnsession) — do NOT spawn via Task tool, run…
test-engineer
Use this agent as a distinguished Test Architecture and Engineering authority. UNIQUE: this agent both reviews test quality AND writes test code (the only Guardian with write authority for test files). Covers test strategy design, unit/integration/contract/E2E test creation, performance testing, chaos engineering…
backend-development-test-automator
Create comprehensive test suites including unit, integration, and E2E tests. Supports TDD/BDD workflows. Use for test creation during feature development.
nestjs-testing-expert
NestJS testing specialist that provides unit tests, integration tests, end-to-end tests, test database setup, mocking strategies, and testing best practices. Use proactively when writing tests for NestJS applications, setting up testing infrastructure, creating test fixtures, mocking dependencies, or implementing…
test-generator
Generates comprehensive test suites using TDD patterns. Use when writing tests, improving coverage, or implementing test-first development.
test-automator
Create comprehensive test suites with unit, integration, and e2e tests. Sets up CI pipelines, mocking strategies, and test data. Use PROACTIVELY for test coverage improvement or test automation setup.