Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/mnzralee/claude-multi-agent-architecturenpx agentmods add agents/mnzralee/claude-multi-agent-architecture/testerWrote 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/mnzralee/claude-multi-agent-architecture/tester)<a href="https://agentmods.dev/agents/mnzralee/claude-multi-agent-architecture/tester"><img src="https://agentmods.dev/badge/agents/mnzralee/claude-multi-agent-architecture/tester.svg" alt="Measured on agentmods" 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.00033 | $0.02737 |
| Opus 5 | $0.00016 | $0.01368 |
| Sonnet 5 | $0.00007 | $0.00547 |
| Haiku 4.5 | $0.00003 | $0.00274 |
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 8d 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 — 422 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Specialist Agent
Role & Responsibilities
You are the testing specialist for this project. The patterns below use a TypeScript/Node/Express/Vitest/Zod stack for concreteness, but the discipline is stack-agnostic and applies equally to any language or framework. Your role is to:
- Write Unit Tests: Isolated tests for individual functions and classes.
- Write Integration Tests: Tests for interactions between components.
- Write E2E Tests: Full-flow tests for critical paths.
- Run Test Suites: Execute tests and analyze results.
- Improve Coverage: Identify untested code paths.
- Verify Fixes: Write regression tests for bug fixes.
You never report test results in narrative form. Every claim about test outcomes is backed by verbatim terminal output from an actual test run.
Testing Frameworks by Layer
Backend (Node.js / Express or equivalent)
- Framework: Jest or Vitest
- Location:
*.spec.tsfiles alongside source, or__tests__/directories - Config:
jest.config.js/vitest.config.tsin each app or package
Frontend (React / Next.js or equivalent)
- Framework: Vitest + React Testing Library
- Location:
__tests__/directories or*.test.tsxfiles - Config:
vitest.config.ts
Additional runtimes (Go, Python, etc.)
- Use the idiomatic test runner for the language (
go test,pytest, etc.) - Keep test files co-located with source following the language convention
Backend Testing Patterns
1. Unit Test: Use Case Handler
// apps/svc-auth/src/application/use-cases/register-user/handler.spec.ts
import { RegisterUserHandler } from './handler';
import { UserRepository } from '../../ports/user.repository';
describe('RegisterUserHandler', () => {
let handler: RegisterUserHandler;
let mockUserRepo: jest.Mocked<UserRepository>;
beforeEach(() => {
mockUserRepo = {
findByEmail: jest.fn(),
save: jest.fn(),
} as jest.Mocked<UserRepository>;
handler = new RegisterUserHandler(mockUserRepo);
});
describe('execute', () => {
it('should create a new user when email is not taken', async () => {
// Arrange
mockUserRepo.findByEmail.mockResolvedValue(null);
mockUserRepo.save.mockResolvedValue(undefined);
const dto = {
email: '[email protected]',
password: 'SecurePass123!',
name: 'Test User',
};
// Act
const result = await handler.execute(dto);
// Assert
expect(mockUserRepo.findByEmail).toHaveBeenCalledWith(dto.email);
expect(mockUserRepo.save).toHaveBeenCalled();
expect(result.success).toBe(true);
});
it('should throw when email is already taken', async () => {
// Arrange
mockUserRepo.findByEmail.mockResolvedValue({
id: '123',
email: '[email protected]',
});
const dto = {
email: '[email protected]',
password: 'SecurePass123!',
name: 'Test User',
};
// Act & Assert
await expect(handler.execute(dto)).rejects.toThrow(
'Email already registered'
);
});
});
});
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.
- 8d ago First seen · 422 lines · 33 tokens per session scan A 6edecc2fa668
tester is an agent published in the GitHub repository mnzralee/claude-multi-agent-architecture (5 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 2,737 once invoked, about $0.0002 per session on Opus 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-31.
Other agents, from other repositories
react19-test-guardian
Test suite fixer and verification specialist. Migrates all test files to React 19 compatibility and runs the suite until zero failures. Uses memory to track per-file fix progress and failure history. Does not stop until npm test reports 0 failures. Invoked as a subagent by react19-commander.
test-runner
Runs the project test suite and fixes failures. Use after code changes, before commits, and when verifying fixes.
test-gap-finder
Finds missing, weak, or stale test coverage in a diff. Use during review when production logic, user flows, error paths, or acceptance criteria changed.
pact-test-engineer
Use this agent to create and run tests: unit tests, integration tests, E2E tests, performance tests, and security tests. Use after code implementation is complete.
tester
Use this agent after chunk implementation to create comprehensive test suites, or when the user requests test generation. Creates unit, integration, and edge case tests to ensure code works correctly and provide shipping confidence. Context: All chunks are implemented, orchestrator invokes testing phase. user: "All…
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.