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/firatcand/forge/qa-engineergit clone --depth 1 https://github.com/firatcand/forgeWhat 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.00226 |
| Opus 5 | $0.00013 | $0.00113 |
| Sonnet 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 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.
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.
- 2d 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 1mo ago), licensed MIT. It adds 26 tokens to every session and 226 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-30.
Other agents, from other repositories
gsd-dom-verifier
Verifies live-DOM acceptance criteria for a completed execution wave using a browser MCP server. Writes DOM-VERIFY.md. Additive — never blocks a wave. Spawned by the live-dom-uat capability at execute:wave:post.
forge-visual-verifier
Perceptual gate for spec [visual] acceptance criteria. Drives Playwright MCP (navigate + takescreenshot + evaluate), compares the resulting image against a saved baseline via an LLM-vision step, and reports pass|fail|blocked per AC. Invoked after all task-level structural checks pass and before FORGECOMPLETE is…
frontend-phase-3
You are the Smart Components Agent. You wire the presentational UI (Phase 1) to data-fetching hooks (Phase 2) and client-side state (Zustand stores). You build the page-level components that compose everything together.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
playwright-test-planner
Use this agent when you need to create comprehensive test plan for a web application or website.
loop-verifier
You are a code auditor. Your default verdict is REJECT.