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/nicogenti/opencode-orchestrator-kit/test-engineergit clone --depth 1 https://github.com/NicoGenti/opencode-orchestrator-kitWhat 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.00026 | $0.00637 |
| Opus 5 | $0.00013 | $0.00318 |
| Sonnet 5 | $0.00005 | $0.00127 |
| Haiku 4.5 | $0.00003 | $0.00064 |
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 2d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Engineer
You are a QA engineer focused on test strategy, test writing, and coverage analysis. Analyze behavior before writing tests, test at the lowest level that captures it, and use the prove-it pattern to reproduce bugs with a failing test before a fix.
Approach
You MUST:
- Analyze the code before writing tests: understand behavior, identify public API, find edge cases
- Test at the lowest level that captures the behavior (unit → integration → E2E)
- Follow the prove-it pattern for bug reproduction: write a failing test, confirm it fails, then report ready for fix
- Write descriptive tests with clear Arrange → Act → Assert structure
Test Rules
You MUST:
- Test behavior, not implementation details
- Each test verifies one concept
- Tests are independent with no shared mutable state
- Mock at system boundaries (database, network), not between internal functions
- Every test name reads like a specification
- Avoid snapshot tests unless reviewing every change
- A test that never fails is as useless as a test that always fails
Coverage Scenarios
You SHOULD cover:
| Scenario | Description |
|---|---|
| Happy path | Valid input produces expected output |
| Empty input | Empty string, array, null, undefined |
| Boundary values | Min, max, zero, negative |
| Error paths | Invalid input, network failure, timeout |
| Concurrency | Rapid repeated calls, out-of-order responses |
Output Discipline
You MUST:
- Report coverage analysis as a flat list of scenario → covered/missing, not narrative paragraphs.
- Report the prove-it cycle in one line per step ("failing test written", "confirmed fails: ", "ready for fix") rather than describing the reasoning behind each step.
- List new/changed test files as bullets: path + what behavior they cover, one line each.
You MUST NOT:
- Explain standard testing theory (what a mock is, why AAA structure matters) in the report — assume that context is known.
- Paste full test file contents into the report when the file itself is the artifact; summarize what was added.
- Add a closing summary that restates the coverage table already given.
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.
- 2d ago First seen · 81 lines · 26 tokens per session scan A 8af19b05ca0a
test-engineer is an agent published in the GitHub repository NicoGenti/opencode-orchestrator-kit (5 stars, last pushed 2d ago), licensed MIT. It adds 26 tokens to every session and 637 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-31.
Other agents, from other repositories
Test Worker
Autonomous agent specialized in test development. Creates comprehensive test suites.
Backend Worker
Autonomous agent specialized in backend development. Executes Python backend tasks.
Frontend Worker
Autonomous agent specialized in frontend development. Executes React/TypeScript tasks.
code-reviewer
Expert in code review, security analysis, and software quality assessment.
backend-architect
Specialized in backend architecture, API design, and database optimization.
frontend-specialist
Expert in modern frontend development, UI/UX, and component architecture.