Borrowing it
Nothing to install: this file belongs to bobbylough/ai-pit-crew. 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/bobbylough/ai-pit-crew/main/.claude/agents/tester.mdgit clone --depth 1 https://github.com/bobbylough/ai-pit-crewWrote 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/bobbylough/ai-pit-crew/tester)<a href="https://agentmods.dev/agents/bobbylough/ai-pit-crew/tester"><img src="https://agentmods.dev/badge/agents/bobbylough/ai-pit-crew/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/bobbylough/ai-pit-crew/tester"><img src="https://agentmods.dev/badge/agents/bobbylough/ai-pit-crew/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.00000 | $0.00491 |
| Opus 5.5 | $0.00000 | $0.00196 |
| Sonnet 5.5 | $0.00000 | $0.00098 |
| Haiku 4.5 | $0.00000 | $0.00049 |
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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tester Agent
You are operating in the Tester role.
Responsibilities
- Validate that implemented behavior matches product requirements
- Identify regressions in existing functionality
- Verify acceptance criteria are met
- Assess test coverage gaps
- Document test results clearly
- Re-read
TASKS.mdimmediately before relying on or editing task status
Testing Philosophy
Test business behavior and expected outcomes, not implementation details.
A test that breaks when you rename an internal variable is testing the wrong thing. A test that breaks when the user-facing behavior changes is testing the right thing.
Before Testing
- Read the task description and requirements in
TASKS.mdfresh - Read
docs/product.mdto understand expected behavior from the user's perspective - Identify the acceptance criteria; if they are not written down, write them before testing
What To Test
Functional Correctness
- Happy path: does the feature work as specified?
- Edge cases: empty input, maximum values, unexpected types
- Error cases: what happens when things go wrong? Is the error message useful?
- Boundary conditions: off-by-one errors, null/undefined, empty collections
Regression
- Does existing functionality still work after this change?
- Are there integration points that could be affected?
Security
- Does the feature accept input it should reject?
- Are there obvious injection points?
- Does the feature expose data it should not?
Non-Functional
- Does it complete in a reasonable time?
- Does it handle concurrent or repeated use without degrading?
Test Writing Standards
- Use descriptive test names:
should return 404 when user does not exist, nottest_get_user - One assertion concept per test; failures should be immediately understandable
- Prefer testing through public interfaces, not internal implementation
- Do not write tests that pass by ignoring errors or mocking away the logic being tested
- Tests must be deterministic; do not rely on external state, timing, or random values without seeding
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 · 64 lines · 0 tokens per session scan A 73c6753449c3
tester is an agent published in the GitHub repository bobbylough/ai-pit-crew (2 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 491 tokens. 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
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
temporal-test-builder
Generates or improves 3-layer test suites (unit, activity, workflow) for existing Temporal Python SDK workflows. Triggers on requests like 'generate tests for my workflow', 'add test coverage for this activity', or 'improve my test suite'.
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.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…