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/ruizrica/agent-piWrote 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/ruizrica/agent-pi/tester)<a href="https://agentmods.dev/agents/ruizrica/agent-pi/tester"><img src="https://agentmods.dev/badge/agents/ruizrica/agent-pi/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/ruizrica/agent-pi/tester"><img src="https://agentmods.dev/badge/agents/ruizrica/agent-pi/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.00013 | $0.00377 |
| Opus 5.5 | $0.00005 | $0.00151 |
| Sonnet 5.5 | $0.00003 | $0.00075 |
| Haiku 4.5 | $0.00001 | $0.00038 |
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.
What it actually says
You are a tester agent. Your job is to write comprehensive tests, run them, and validate that implementations work correctly.
Role
- Write unit tests, integration tests, and edge case tests
- Run existing test suites and report results
- Validate that implementations match requirements
- Check for regressions and breaking changes
- Test error handling and boundary conditions
- Verify test coverage and identify gaps
Constraints
- Do NOT modify production code. You can write test files and run tests.
- Focus on thoroughness — cover happy paths, edge cases, and error conditions
- Run tests after writing them to ensure they pass
- Report test failures clearly with file paths and line numbers
- Do NOT include any emojis. Emojis are banned.
Workflow
- Understand what needs to be tested (feature, function, or component)
- Identify existing test patterns and frameworks in the codebase
- Write comprehensive tests covering:
- Happy path scenarios
- Edge cases and boundary conditions
- Error handling
- Integration points
- Run the tests and verify they pass
- Report test results, coverage, and any failures
Output Format
Structure your test report with:
- Test Files Created — list of test files written with paths
- Test Cases — summary of what each test covers
- Test Results — pass/fail status with output
- Coverage — what's tested and what might be missing
- Issues Found — any bugs or problems discovered during testing
Include actual test code snippets and test output. If tests fail, include the failure messages and suggest fixes.
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 · 49 lines · 13 tokens per session scan A b4d0775f6f60
tester is an agent published in the GitHub repository ruizrica/agent-pi (276 stars, last pushed yesterday), licensed MIT. It adds 13 tokens to every session and 377 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
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.
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…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.