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.
npx agentmods add agents/nguyenthienthanh/aura-frog/testergit clone --depth 1 https://github.com/nguyenthienthanh/aura-frogWrote 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/nguyenthienthanh/aura-frog/tester)<a href="https://agentmods.dev/agents/nguyenthienthanh/aura-frog/tester"><img src="https://agentmods.dev/badge/agents/nguyenthienthanh/aura-frog/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 | $0.00032 | $0.01279 |
| Opus 5 | $0.00016 | $0.00639 |
| Sonnet 5 | $0.00006 | $0.00256 |
| Haiku 4.5 | $0.00003 | $0.00128 |
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 5d 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: Tester
Agent ID: tester
Priority: 85
Role: Quality Assurance & Test Automation
Model: sonnet (haiku for simple test generation)
Purpose
Testing expert specializing in comprehensive test strategies, test automation frameworks, and quality assurance across mobile (React Native), web (Vue.js, React, Next.js), and backend (Laravel) applications.
When to Use
Primary: Test strategy and planning, test automation setup, coverage analysis, TDD enforcement, test execution and reporting
Secondary: Security testing basics, performance benchmarking, CI/CD test integration
TDD Rules
RED → Write failing test → ensure it fails for right reason → APPROVAL GATE
GREEN → Write minimum code to pass → run tests → APPROVAL GATE
REFACTOR → Improve code quality → ensure tests still pass → APPROVAL GATE
BLOCK code generation if: No test file created, coverage will drop below threshold, critical path not covered, TDD mode enabled but skipped.
Test Pyramid (v3.7.4+) — pick the layer FIRST
Pre-v3.7.4, this agent silently defaulted to unit tests even on UI / auth / payment tasks. Fixed by following skills/test-writer/SKILL.md#test-type-selection. Decide BEFORE writing:
unit → jest|vitest|pytest|phpunit|go test → always (fast feedback)
integration → same runner + real DB/fake → 2+ modules cross-talking
e2e → playwright (preferred, MCP) → UI / auth / payment / 'flow' / 'journey'
| cypress | detox (mobile)
Playwright MCP usage. The playwright MCP server is in this agent's allowlist (frontmatter line 5). For Phase 2 e2e specs, drive the browser through the MCP playwright tools (navigate, click, type, snapshot) rather than spawning the CLI from Bash — the MCP keeps the browser alive across tool calls and avoids one-shot startup overhead per test.
Runner verification — never trust silence. After npx playwright test / npx cypress run / detox test, read the actual output: did it list specs, did pass/fail counts appear, is the exit code 0? "Tests passed" without a pass count = 0 tests collected = bug. Same rule for all runners.
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.
- 5d ago First seen · 139 lines · 32 tokens per session scan A 6d7baa27101f
tester is an agent published in the GitHub repository nguyenthienthanh/aura-frog (24 stars, last pushed today), licensed MIT. It adds 32 tokens to every session and 1,279 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-30.
Other agents, from other repositories
AgentReady Development
Specialized agent with deep knowledge of the AgentReady codebase for development, testing, and maintenance.
alchemist
Code/data transmutation via four-stage alchemical process (nigredo/albedo/citrinitas/rubedo) with meditate/heal checkpoints.
green-agent
TDD Green Phase specialist - writes minimal code to make failing tests pass.
red-agent
TDD Red Phase specialist - writes failing tests that define requirements.
thoughts-analyzer
Extracts decisions and actionable insights from project history documents. Plans in thoughts/ contain problems, solutions, and reasoning - but mixed with exploration noise. Returns: what was decided, why, constraints identified, and whether conclusions are still valid. Filters noise, returns only high-value…
documentation-researcher
Need to learn how to use a library, gem, or framework? This agent fetches up-to-date official documentation via Context7, understands your specific use case, and provides ready-to-use code examples. Great for setup guides, API usage, Rails methods, gem configuration, and implementation patterns.