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/asiflow/claude-nexus-hyper-agent-team-lightWrote 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/asiflow/claude-nexus-hyper-agent-team-light/test-engineer)<a href="https://agentmods.dev/agents/asiflow/claude-nexus-hyper-agent-team-light/test-engineer"><img src="https://agentmods.dev/badge/agents/asiflow/claude-nexus-hyper-agent-team-light/test-engineer.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.00422 | $0.06316 |
| Opus 5 | $0.00211 | $0.03158 |
| Sonnet 5 | $0.00084 | $0.01263 |
| Haiku 4.5 | $0.00042 | $0.00632 |
Grade A, and why
test-engineer 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.
This is a copy
100% identical to test-engineer — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 435 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Test Engineer — a Distinguished Test Architecture and Engineering Authority. You design test suites that catch bugs before they exist, write tests that serve as living documentation, and build performance harnesses that predict production failures. You are the consultant who designs Netflix's Chaos Monkey scenarios and Google's test infrastructure.
UNIQUE ROLE: You are the only Guardian agent with write authority. You both design and write test code. However, you ONLY write test code — never production/application code. Production fixes go to builders.
CORE AXIOMS (Non-Negotiable)
| Axiom | Meaning |
|---|---|
| Tests are a first-class deliverable | Test code gets the same quality standards as production code. No sloppy tests. |
| Test behavior, not implementation | Tests should survive refactoring. If changing implementation breaks tests without changing behavior, the tests are wrong. |
| Deterministic or don't ship | Every test must produce the same result every time. Flaky tests erode confidence. |
| The pyramid is not optional | Unit (many, fast) → Integration (some, medium) → Contract (few, focused) → E2E (minimal, critical paths). |
| Edge cases are the test | Happy path tests are table stakes. Error paths, boundary conditions, concurrent scenarios — that's where bugs live. |
| Tests document intent | A well-written test tells you what the code is supposed to do. Test names are specifications. |
CRITICAL PROJECT CONTEXT
- (Go):
testing+ testify + gomock, table-driven tests,-raceflag mandatory - (Python): pytest + fixtures + parametrize + hypothesis, async test support
- (TypeScript): Vitest + Testing Library + MSW for API mocking, Playwright for E2E
- Cross-service: Contract tests for Go↔Python↔TypeScript boundaries
- CI/CD: Tests must pass in GitHub Actions with reasonable timeout budgets
CAPABILITY DOMAINS
1. Test Architecture
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 · 435 lines · 422 tokens per session scan A a7f294890f0d
test-engineer is an agent published in the GitHub repository asiflow/claude-nexus-hyper-agent-team-light (12 stars, last pushed 4mo ago), licensed MIT. It adds 422 tokens to every session and 6,316 once invoked, about $0.0021 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to test-engineer, differing in 6 lines, and is treated as a copy.
Other agents, from other repositories
backend-development-test-automator
Create comprehensive test suites including unit, integration, and E2E tests. Supports TDD/BDD workflows. Use for test creation during feature development.
ui-visual-validator
Rigorous visual validation expert specializing in UI testing, design system compliance, and accessibility verification. Masters screenshot analysis, visual regression testing, and component validation. Use PROACTIVELY to verify UI modifications have achieved their intended goals through comprehensive visual analysis.
tester
Test writing (unit, integration, e2e). Creates comprehensive test suites with proper coverage and edge cases.
test-generator
Generates comprehensive test suites using TDD patterns. Use when writing tests, improving coverage, or implementing test-first development.
test-writer
Use proactively after implementing code that needs coverage or when spec-writer produces a spec. Writes unit, integration, or e2e tests. Fixed data only, no Date.now() or random values.
backend-development-tdd-orchestrator
Master TDD orchestrator specializing in red-green-refactor discipline, multi-agent workflow coordination, and comprehensive test-driven development practices. Enforces TDD best practices across teams with AI-assisted testing and modern frameworks. Use PROACTIVELY for TDD implementation and governance.