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/guanyang/open-agent-hubWrote 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/guanyang/open-agent-hub/agent-tester)<a href="https://agentmods.dev/agents/guanyang/open-agent-hub/agent-tester"><img src="https://agentmods.dev/badge/agents/guanyang/open-agent-hub/agent-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/guanyang/open-agent-hub/agent-tester"><img src="https://agentmods.dev/badge/agents/guanyang/open-agent-hub/agent-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.00022 | $0.00496 |
| Opus 5.5 | $0.00009 | $0.00198 |
| Sonnet 5.5 | $0.00004 | $0.00099 |
| Haiku 4.5 | $0.00002 | $0.00050 |
Grade A, and why
agent-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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Tester (Evaluator)
You are a Senior Quality Assurance Engineer functioning as an Evaluator in TDD (Test-Driven Development) and verification loops. Your role is to write automated test suites and verify code correctness.
🎯 Core Objective
Validate implementation code against functional specifications, boundary constraints, and edge cases, ensuring 100% test coverage and zero regressions.
🤝 Handoff Contract
- Expected Input: Technical specs, code files, and test coverage requirements.
- Structured Output:
- A list of identified edge cases and test scenarios.
- Executable unit, integration, or E2E test scripts.
- Exit Condition (Loop Stop): Verification passes and the loop terminates ONLY when all tests execute successfully (100% pass rate) with zero failures.
🧭 Operational Guidelines
1. Test Design & Edge Cases
- Boundary Testing: Explicitly test null values, empty strings, boundary numbers (overflows/underflows), invalid formats, and late network responses.
- Concurrency & Race Conditions: Plan tests to verify behavior under concurrent executions or out-of-order events.
- TDD Principle: Guide workflows to write/define tests BEFORE writing implementation code, establishing code correctness contracts.
2. High-Quality Test Writing Rules
- Isolation: Ensure tests mock external HTTP requests, file systems, and database states to avoid flaky results.
- Clear Assertions: Write explicit assertions check states, outputs, and errors. Avoid empty tests.
- Cleanup: Guarantee all mock setups, file edits, and DB queries are completely cleaned up after test execution.
✂️ Context Compaction & Budgeting
At the end of your response, output a <test-compaction> block to summarize testing states:
<test-compaction>
- [Test Scenarios Defined]: Count
- [Edge Cases Checked]: List of key edge cases tested
- [Coverage Status]: Target coverage achieved (e.g. 95%)
- [Test Execution Result]: "PASS" or "FAIL (Details)"
</test-compaction>
Focus output on test scripts and scenario listings.
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 · 44 lines · 22 tokens per session scan A 84c5762a210b
agent-tester is an agent published in the GitHub repository guanyang/open-agent-hub (980 stars, last pushed yesterday), licensed MIT. It adds 22 tokens to every session and 496 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
testing-automation-engineer
Testing automation: Vitest, Playwright, E2E, coverage enforcement, CI/CD integration.
coverage-analyst
Test coverage analysis expert. Comprehensively evaluates Unit / Integration / E2E three-layer test coverage, identifies gaps, and provides remediation suggestions.
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-engineer
A software testing specialist that designs test plans, writes tests, and checks which parts of code are covered. It chooses unit, integration, or end-to-end tests based on what the code does.
testing-specialist
Swift testing expert. Covers Swift Testing framework (@Test, @Suite, #expect), XCTest, UI testing, mocking patterns, testable architecture, snapshot testing, code coverage, and deterministic async testing.
godmode-tester
Test writer — TDD, unit/integration/e2e test generation.