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/asiflow/claude-nexus-hyper-agent-team/test-engineergit clone --depth 1 https://github.com/asiflow/claude-nexus-hyper-agent-teamWrote 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/test-engineer)<a href="https://agentmods.dev/agents/asiflow/claude-nexus-hyper-agent-team/test-engineer"><img src="https://agentmods.dev/badge/agents/asiflow/claude-nexus-hyper-agent-team/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 | $0.00422 | $0.06326 |
| Opus 5 | $0.00211 | $0.03163 |
| Sonnet 5 | $0.00084 | $0.01265 |
| Haiku 4.5 | $0.00042 | $0.00633 |
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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- test-engineer — 100% identical, 6 lines differ
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.
- 5d ago First seen · 435 lines · 422 tokens per session scan A 7b63be2c64e8
test-engineer is an agent published in the GitHub repository asiflow/claude-nexus-hyper-agent-team (18 stars, last pushed 3mo ago), licensed MIT. It adds 422 tokens to every session and 6,326 once invoked, about $0.0021 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
data-engineer
Build scalable data pipelines, modern data warehouses, and real-time streaming architectures. Implements Apache Spark, dbt, Airflow, and cloud-native data platforms. Use PROACTIVELY for data pipeline design, analytics infrastructure, or modern data stack implementation.
backend-api-security-backend-security-coder
Expert in secure backend coding practices specializing in input validation, authentication, and API security. Use PROACTIVELY for backend security implementations or security code reviews.
basic-agents
A basic agent uses a predefined strategy with a simple execution flow that works for most common use cases. It accepts a string input (a question, request, or task description) and sends this input to the configured LLM. The LLM may decide to call provided tools. The agent will execute the tools and send the results…
shadow-auditor
Audits agent decisions and session outcomes for compliance and quality. Assign as a shadow for end-of-session review.
relay-reviewer
A code review agent that checks for bugs, regressions, and testing gaps then reports via Agent Relay. Use when you need a second pair of eyes on changes.
config-safety-reviewer
Configuration safety specialist focusing on production reliability, magic numbers, pool sizes, timeouts, and connection limits. Use proactively for configuration changes and production safety reviews.