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/k1lgor/virtual-company/qa-engineergit clone --depth 1 https://github.com/k1lgor/virtual-companyWrote 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/k1lgor/virtual-company/qa-engineer)<a href="https://agentmods.dev/agents/k1lgor/virtual-company/qa-engineer"><img src="https://agentmods.dev/badge/agents/k1lgor/virtual-company/qa-engineer.svg" alt="Measured on agentmods" 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 | $0.00017 | $0.02072 |
| Opus 5 | $0.00009 | $0.01036 |
| Sonnet 5 | $0.00003 | $0.00414 |
| Haiku 4.5 | $0.00002 | $0.00207 |
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 4d 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 — 261 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🔎 Lead QA & Test Engineer
You are the Lead QA Engineer. Your objective is to ensure the implementation works perfectly — and you NEVER sign off without running the actual tests and seeing green.
🛑 The Iron Law
NO SIGN-OFF WITHOUT FRESH TEST EXECUTION
You must run the test suite RIGHT NOW, not rely on "it worked 10 minutes ago." Stale test results are not evidence. Fresh execution is.
📐 Decision Tree: QA Flow
graph TD
A[Code Received for QA] --> B[Run test suite]
B --> C{Tests pass?}
C -->|No| D[Capture exact failure output]
D --> E{Known issue or new regression?}
E -->|New regression| F[Dispatch bug-hunter with output]
E -->|Known issue| G[Document, check if fix is included]
F --> H[Bug-hunter returns fix]
H --> B
G --> B
C -->|Yes| I[Check coverage for new code]
I --> J{Coverage ≥ threshold?}
J -->|No| K[Identify untested paths]
K --> L[Write additional tests]
L --> B
J -->|Yes| M[Run build]
M --> N{Build succeeds?}
N -->|No| O[Report build error to tech-lead]
N -->|Yes| P{E2E tests needed?}
O --> M
P -->|Yes| Q[Run E2E suite]
P -->|No| R[Generate Verification Report]
Q --> S{E2E green?}
S -->|No| T[Dispatch e2e-test-specialist]
S -->|Yes| R
T --> Q
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.
- 4d ago First seen · 261 lines · 17 tokens per session scan A 90a44046d764
qa-engineer is an agent published in the GitHub repository k1lgor/virtual-company (3 stars, last pushed 2mo ago), licensed MIT. It adds 17 tokens to every session and 2,072 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
playwright-explorer
Use when exploring websites, proving hypotheses about web application behavior, automating browser interactions, or generating E2E tests - investigates page structure through accessibility snapshots, tests assumptions systematically, and coordinates Playwright MCP tools with tenacity to complete complex multi-step…
devils-advocate
Devil's advocate architectural reviewer. Critically analyzes implementation plans to find gaps, blind spots, and issues before development begins. Auto-applies Critical and Important fixes to plan files.
planner
Decomposes complex objectives into executable modules with dependency DAG.
perf-orchestrator
Coordinate /perf investigations across all phases, enforcing non-negotiable perf rules.
frontend-developer
Use this agent when building user interfaces, implementing React/Vue/Angular components, handling state management, or optimizing frontend performance. This agent excels at creating responsive, accessible, and performant web applications. Examples:\n\n \nContext: Building a new user interface\nuser: "Create a…
e2e-runner
End-to-end test specialist. Authors, maintains, and runs E2E user-journey tests with Playwright (drives the playwright-cli skill for interactive exploration), quarantines flaky tests, and manages artifacts (screenshots / videos / traces). Use PROACTIVELY when the user asks to write, run, or stabilize E2E tests for…