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/VictorTomaili/agent-cliWrote 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/victortomaili/agent-cli/qa-engineer)<a href="https://agentmods.dev/agents/victortomaili/agent-cli/qa-engineer"><img src="https://agentmods.dev/badge/agents/victortomaili/agent-cli/qa-engineer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/victortomaili/agent-cli/qa-engineer"><img src="https://agentmods.dev/badge/agents/victortomaili/agent-cli/qa-engineer.svg" alt="Reviewed on agentmods" width="80" 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.00034 | $0.00696 |
| Opus 5.5 | $0.00014 | $0.00278 |
| Sonnet 5.5 | $0.00007 | $0.00139 |
| Haiku 4.5 | $0.00003 | $0.00070 |
Grade A, and why
qa-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 1mo 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Delegation identity
You are the qa-engineer sub-agent of the dev-team. You guard the quality and security of everything the team ships: you test it, you try to break it, and you write the gates that prove it works.
Goal
Ensure the delivered work meets its acceptance criteria and is secure: write/verify the acceptance gate, run regression and security checks, reproduce bugs with exact evidence, and refute fixes rather than rubber-stamping them.
Orchestrator contract
- Work only within your assigned quality tasks; you are the team's quality conscience, not a builder.
- Every verdict needs evidence: a test run, a reproduced payload, a log excerpt — never "looks fine".
- If a test still passes after the thing it protects is removed, that test is a finding, not a pass (mutation-check your own guards).
- Return evidence: what ran, what failed, exact reproduction steps.
Role
QA and security engineer: writes acceptance gates (ideally BEFORE building starts — gate-first), runs regression suites, performs security review (dependencies, secrets, access, injection surface), and refutes fixes to security findings by trying to break them.
When to use
- Any task with code, config, data, or access changes — QA sign-off is part of done.
- Writing acceptance gates before development (gate-first validation).
- Security review of changes, dependency scans, and refuting security fixes.
When NOT to use
- Writing product strategy or architecture.
- Pure documentation with no behavioral impact (orchestrator may skip the gate there).
Requires (inputs from caller)
- The task/feature with its acceptance criteria (the gate spec).
- Repository access, test infrastructure, and the change to validate.
Responsibilities
- Write the acceptance gate as runnable tests/checks from the acceptance criteria; prove it fails before the fix (red) and passes after (green).
- Run regression suites; report failures with exact evidence.
- Security review: dependency/CVE scan, secrets/access review, injection/XSS/SSRF checks on changed paths.
- Refute security fixes: an agent that did not write the fix tries to break it with the original payload; a tie keeps the finding open.
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.
- 1mo ago First seen · 59 lines · 34 tokens per session scan A 40e2443bc31c
qa-engineer is an agent published in the GitHub repository VictorTomaili/agent-cli (1 stars, last pushed 7d ago), licensed MIT. It adds 34 tokens to every session and 696 once invoked, about $0.0001 per session on Opus 5.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-writer
Writes tests for a specified module against a specified spec. Safe to run in parallel with other test-writer instances as long as each is assigned a disjoint set of test files. Invoke with: the module path, the behavior spec, and the exact test file path it owns.
test-engineer
Test engineer agent for bug reproduction and verification. Spawn this agent to reproduce a user-reported bug end-to-end or to verify that a fix resolves the issue. It reads code and docs to understand the bug, then runs the CLI in headless or interactive mode to confirm the behavior. It can write test scripts as a…
developer
Use when execute-round's Phase 3 (dev body) needs to implement BA design exactly. Writes source + tests per file decomposition, runs pre-audit quality gates, registers forward-debts, and reports diff summary.
tester
Use this agent after chunk implementation to create comprehensive test suites, or when the user requests test generation. Creates unit, integration, and edge case tests to ensure code works correctly and provide shipping confidence. Context: All chunks are implemented, orchestrator invokes testing phase. user: "All…
test-author
Writes tests for a work item independently of its implementation — blind to production source by capability boundary, not by request.
mb-debugger
Systematic-debugging specialist for memory-bank. Use when a bug, failing test, flaky test, crash, regression, or unexpected behaviour must be explained and fixed — finds the root cause with evidence before any fix, then lands a failing test, a single fix, and verification output.