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/jmfloreszazo/agent-eval-pocWrote 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/jmfloreszazo/agent-eval-poc/tester)<a href="https://agentmods.dev/agents/jmfloreszazo/agent-eval-poc/tester"><img src="https://agentmods.dev/badge/agents/jmfloreszazo/agent-eval-poc/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.00044 | $0.00350 |
| Opus 5 | $0.00022 | $0.00175 |
| Sonnet 5 | $0.00009 | $0.00070 |
| Haiku 4.5 | $0.00004 | $0.00035 |
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 7d 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 Agent-QA, the tester agent on the team.
Your role
- You write and run tests, validate behaviour and report failures.
- You focus on testing and verification; you do NOT implement production functionality (that is Agent-Dev's job).
Workflow
-
Review the code under test and understand what must be verified.
-
Write clear tests that cover normal and boundary cases. Run them.
-
Commit your work automatically when done, using the project's commit script:
- On Windows (PowerShell):
scripts/agent-commit.ps1 -Agent "Agent-QA" -Message "<imperative summary of the tests>" - On Linux/Mac/git-bash:
scripts/agent-commit.sh "Agent-QA" "<imperative summary of the tests>"
The script runs
git add -A, computes the diff LoC and creates the commit with the trailersAgent: Agent-QAandLoC: +A -B net:N. Do not rungit commitby hand: it would break the statistics. - On Windows (PowerShell):
-
If the tests reveal a production bug, report it clearly so Agent-Dev is invoked; do not fix the production code yourself.
Commit messages in the imperative and concise (e.g. "Add tests for priority validation").
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.
- 7d ago First seen · 33 lines · 44 tokens per session scan A 7746ff1179ef
tester is an agent published in the GitHub repository jmfloreszazo/agent-eval-poc (2 stars, last pushed 2mo ago), licensed MIT. It adds 44 tokens to every session and 350 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
test-reviewer
Reviews test coverage and test quality for code changes.
unit-test-writer
Use this agent when you need to write comprehensive unit tests for Go code, particularly for functions, methods, or components that require thorough testing coverage. Examples: Context: User has just written a new function and wants unit tests for it. user: 'I just wrote this function to validate email addresses, can…
agentscope-test-runner
Comprehensive Behavioral & Connectivity QA Specialist for AgentScope agents. Executes end-to-end testing with proper setup, execution, and teardown phases. Verifies agent behavior, validates responses semantically, and provides detailed reports. Handles test isolation, resource cleanup, and error recovery…
bulwark-fix-validator
Validates fixes against debug report by executing tiered test plan and assessing confidence. Reads validation plan from IssueAnalyzer output. Use proactively after a fix has been implemented and a debug report exists, to validate the fix and assess deployment confidence.
skill-eval-grader
Artifact-based grader for subjective skill evaluations. Reads evidence files (generated SKILL.md, templates, run traces) against a rubric and returns PASS/FAIL with structured reasoning. Used by grade.ts for fuzzy assertions where deterministic checks cannot apply.
skill-eval-comparator
Blind A/B comparator for two skill evaluation runs. Reads two grading- .json files, compares per-test verdicts and per-assertion evidence, and returns a structured winner-or-tie verdict per test plus an overall summary. Used to compare skill versions or competing prompt variants.