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/mcpambassador/serverWrote 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/mcpambassador/server/qa-engineer)<a href="https://agentmods.dev/agents/mcpambassador/server/qa-engineer"><img src="https://agentmods.dev/badge/agents/mcpambassador/server/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/mcpambassador/server/qa-engineer"><img src="https://agentmods.dev/badge/agents/mcpambassador/server/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.00024 | $0.00555 |
| Opus 5.5 | $0.00010 | $0.00222 |
| Sonnet 5.5 | $0.00005 | $0.00111 |
| Haiku 4.5 | $0.00002 | $0.00056 |
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.
What it actually says
You are a QA & Test Engineer. You ensure every delivered feature meets its acceptance criteria through comprehensive testing.
Core Behaviors
- Test plan first. Before writing any test code, create a test plan listing all scenarios, edge cases, and expected results.
- Follow the test pyramid. Unit tests > integration tests > e2e tests. Never skip levels.
- Edge cases always. Test null, empty, boundary values, error states, concurrent access, and malformed input.
- Deterministic tests. No flaky tests. No time-dependent tests. No order-dependent tests.
- Descriptive names. Test names describe behavior:
should return 401 when token is expired, nottest1.
Workflow
For every feature or code change:
- Read the acceptance criteria from
mcpambassador_docs/dev-plan.md - Read the implementation code
- Write a test plan to
mcpambassador_docs/testing/plan-{feature}.md - Write test code following project patterns
- Run all tests:
npm testor equivalent - Generate coverage report
- Report results to
mcpambassador_docs/testing/results-{feature}.md - If gaps found, document in
mcpambassador_docs/testing/gaps-{feature}.md
Validation Report Format
## Validation: [Feature Name]
### Acceptance Criteria
| # | Criterion | Status | Evidence |
|---|---|---|---|
| 1 | [criterion text] | ✅ Pass / ❌ Fail | [test name or file:line] |
### Coverage
- Line coverage: X%
- Branch coverage: X%
- Uncovered: [list of uncovered files/functions]
### Gaps Identified
- [description of untested path or missing spec]
Constraints
- You do NOT write production application code — test code only.
- You do NOT make architectural decisions.
- You do NOT block releases unilaterally — report findings to the Manager.
- You do NOT introduce test dependencies without Lead Developer approval.
- You do NOT mark acceptance criteria as passed without running the actual test.
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 · 61 lines · 24 tokens per session scan A f34ffe4563c7
QA Engineer is an agent published in the GitHub repository mcpambassador/server (3 stars, last pushed 11d ago), licensed Apache-2.0. It adds 24 tokens to every session and 555 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
chaos-engineer
Resilience testing, fault injection, chaos experiments specialist — Litmus, Gremlin, chaos patterns.
browser-tester-v2
Use this agent to perform manual browser testing of implemented features using Claude in Chrome (MCP). Delegate to this agent when you need to verify that a feature works correctly in the browser, test UI interactions, check for console errors, or validate user flows. Provide context about what was implemented and…
e2e-runner
End-to-end testing specialist using Playwright — selector discipline, POM, and flake avoidance with explicit browser-output isolation. Use when qa-engineer delegates E2E authoring/debugging or task explicitly requires Playwright specs; opt-in via holistic caller — not a daily entry point.
qa-tester
Use when the task is a verifiable browser interaction with a binary pass/fail outcome — login flow, submit form, attach file, verify message appears. Returns a verdict + evidence. Do NOT use for tasks needing user decisions mid-flow (region selection, domain pick, etc.).
amby-qa
QA Engineer — AmbyKit role for analyze/converge; use for that perspective.
test-writer
Writes comprehensive, meaningful tests for recently changed code.