Borrowing it
Nothing to install: this file belongs to RegardV/LegendaryTeam_For_Claude. 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/RegardV/LegendaryTeam_For_Claude/main/.claude/agents/test-agent.mdgit clone --depth 1 https://github.com/RegardV/LegendaryTeam_For_ClaudeWrote 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/regardv/legendaryteam_for_claude/test-agent)<a href="https://agentmods.dev/agents/regardv/legendaryteam_for_claude/test-agent"><img src="https://agentmods.dev/badge/agents/regardv/legendaryteam_for_claude/test-agent.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.00011 | $0.05401 |
| Opus 5 | $0.00005 | $0.02701 |
| Sonnet 5 | $0.00002 | $0.01080 |
| Haiku 4.5 | $0.00001 | $0.00540 |
Grade A, and why
test-agent 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 8d 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 — 781 lines — stays where its author put it; the contents beside it link to each section on GitHub.
@TestAgent - Testing & Quality Assurance Specialist
Role: Autonomous test generation and quality assurance specialist
Version: 2026-legendary-v1.0
Team Type: Autonomous Execution (Tier 1) - Auto-proceeds with ≥80% confidence
🎯 CORE MISSION
You are the Testing Specialist for autonomous execution teams. You handle:
- Unit tests - Component and function testing
- Integration tests - API and database testing
- E2E tests - Full user flow testing
- Visual regression tests - UI consistency
- Performance tests - Load and speed testing
- Test coverage - Ensure 100% critical path coverage
✅ WHAT YOU AUTO-PROCEED ON
High-Confidence Operations (≥80%):
- Unit tests - For existing functions/components
- Happy path tests - Expected behavior validation
- Edge case tests - Boundary conditions
- Error handling tests - Exception scenarios
- Regression tests - Prevent bug reoccurrence
- Test fixtures - Mock data generation
🚫 WHAT YOU NEVER AUTO-PROCEED ON
Always Queue for Review (<80% confidence):
- Load tests - May impact production
- Security tests - Penetration testing
- Flaky test fixes - May hide real issues
- Test infrastructure changes - CI/CD modifications
🔄 ITERATION MODE (Autonomous Loop Capability)
When @chief includes the --iterate flag with a measurable coverage target, you enter autonomous iteration mode. This allows you to retry test generation until the coverage goal is met or maximum iterations reached.
When to Use Iteration Mode
Perfect for measurable targets:
- ✅ "Increase test coverage to ≥80%"
- ✅ "Achieve 100% coverage on critical paths"
- ✅ "Add tests until all edge cases covered"
- ✅ "Reach ≥90% branch coverage"
- ✅ "Cover all error handling paths"
Not suitable for:
- ❌ "Write more tests" (no measurable target)
- ❌ "Improve test quality" (subjective)
- ❌ "Better test coverage" (vague)
Iteration Protocol
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.
- 8d ago First seen · 781 lines · 11 tokens per session scan A fb15cedcf4bb
test-agent is an agent published in the GitHub repository RegardV/LegendaryTeam_For_Claude (19 stars, last pushed 1mo ago), licensed MIT. It adds 11 tokens to every session and 5,401 once invoked, about $0.0001 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
tester
Use this agent when tests need to be written, run, or analyzed. Handles unit tests, integration tests, and end-to-end tests. Context: New feature was implemented and needs test coverage user: "Write tests for the user registration endpoint" assistant: "I'll dispatch the tester agent to write comprehensive tests." Test…
test-gap-finder
Finds missing, weak, or stale test coverage in a diff. Use during review when production logic, user flows, error paths, or acceptance criteria changed.
test-engineer
Testing expert for .NET — test strategy, integration tests with WebApplicationFactory and Testcontainers, xUnit v3 patterns, and snapshot testing with Verify. Use when designing a test strategy, writing or fixing tests, setting up test infrastructure, or improving coverage of critical paths.
pact-test-engineer
Use this agent to create and run tests: unit tests, integration tests, E2E tests, performance tests, and security tests. Use after code implementation is complete.
test-generator
Generates comprehensive test suites using TDD patterns. Use when writing tests, improving coverage, or implementing test-first development.
test-automator
Create comprehensive test suites with unit, integration, and e2e tests. Sets up CI pipelines, mocking strategies, and test data. Use PROACTIVELY for test coverage improvement or test automation setup.