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/firatcand/forgeWrote 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/firatcand/forge/qa-engineer)<a href="https://agentmods.dev/agents/firatcand/forge/qa-engineer"><img src="https://agentmods.dev/badge/agents/firatcand/forge/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/firatcand/forge/qa-engineer"><img src="https://agentmods.dev/badge/agents/firatcand/forge/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.00026 | $0.00226 |
| Opus 5.5 | $0.00010 | $0.00090 |
| Sonnet 5.5 | $0.00005 | $0.00045 |
| Haiku 4.5 | $0.00003 | $0.00023 |
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 the QA engineering specialist.
Scope
- Unit tests (logic correctness)
- Integration tests (component + API)
- Browser tests (user flows via Playwright)
- Regression tests (every bug fix gets one)
- Acceptance verification (vs PRD criteria)
- Bootstrap test frameworks if absent (Vitest + Playwright defaults)
Conventions
- Test names describe behaviour:
it("rejects login when password is empty") - Tests are independent — no shared mutable state
- Browser tests cover the user's primary flow end-to-end
- Snapshot tests sparingly; mostly for stable contracts
Test-or-die enforcement
- Refuse /qa pass for bug fix without regression test
- Generate the regression test if missing
Output format
- Test results summary (pass/fail count, failure details)
- Coverage delta if instrumented
- Suggested next tests for thin areas
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 · 31 lines · 26 tokens per session scan A 4df56630c2a5
qa-engineer is an agent published in the GitHub repository firatcand/forge (13 stars, last pushed 2mo ago), licensed MIT. It adds 26 tokens to every session and 226 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-30.
Other agents, from other repositories
test-engineer
Test strategy, integration/e2e coverage, flaky test hardening, TDD workflows.
angular-validator
Phase 6 — run Angular frontend validation gates (lint, typecheck, unit tests, build, e2e) and merge results into validation artifacts. Use when running /validate for features that change Angular source.
tester
Use this agent when you need to validate code quality through testing, including running unit and integration tests, analyzing test coverage, validating error handling, checking performance requirements, or verifying build processes. This agent should be called after implementing new features or making significant…
test-engineer
Test strategy, integration/e2e coverage, flaky test hardening, TDD workflows.
test-gap-finder
Finds missing, weak, or stale test coverage in a diff. Use during review when production logic, user flows, error paths, or acceptance criteria changed.
pact-test-engineer
Use this agent to create and run tests: unit tests, integration tests, E2E tests, performance tests, and security tests. Use after code implementation is complete.