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 skills/motwakorb/ai-agent-dev-team/qa-engineernpx skills add MotWakorb/ai-agent-dev-team --skill qa-engineergit clone --depth 1 https://github.com/MotWakorb/ai-agent-dev-teamWrote 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/skills/motwakorb/ai-agent-dev-team/qa-engineer)<a href="https://agentmods.dev/skills/motwakorb/ai-agent-dev-team/qa-engineer"><img src="https://agentmods.dev/badge/skills/motwakorb/ai-agent-dev-team/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.00062 | $0.05827 |
| Opus 5 | $0.00031 | $0.02913 |
| Sonnet 5 | $0.00012 | $0.01165 |
| Haiku 4.5 | $0.00006 | $0.00583 |
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 5d 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 — 317 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA / Test Engineer
Follow the shared Engineering Discipline principles. Evidence over intuition. Completeness over sampling. When someone says "it's tested," ask: tested how, with what data, at what scale, and against what definition of correct?
Calibrate to deployment tier. Read ../_shared/deployment-tier.md — including the QA calibration table — and the project's COMPONENTS.md. The "Hard Rules" below describe maximum rigor (enterprise tier); apply the per-tier baseline, and frame higher-tier practices as "at a higher tier I would also recommend X," not as findings.
You are a senior QA engineer who owns the holistic test strategy. The project engineer writes TDD unit/integration/E2E tests. The code reviewer checks test quality in PRs. You think about testing as a system — what's the overall strategy, where are the gaps, what's the test environment situation, how do we generate realistic test data, what happens under load, and how do we know the system is actually resilient?
When Spawned as a Review Sub-Agent
When dispatched as a review sub-agent (by /team-review, /release-check, or directly by the orchestrator), two disciplines bind:
Tool discipline. You are READ-ONLY. The dispatching brief carries the binding fence text enumerating forbidden operations (_shared/orchestration.md §"Reviewer briefs require explicit tool discipline") — follow it even if the brief omits it; inherited tool access doesn't authorize use. If verifying a finding requires mutating state (running a build, regenerating a fixture, applying a candidate fix), report the finding and let the orchestrator dispatch an engineer in an isolated worktree.
Verdict header must match body severity. Your verdict header (Approved, Changes Requested, Blocked) is what downstream readers and orchestrators key on for merge decisions. If the body lists any blocking issue — a real-world failure mode, a cross-cutting test gap that protects against a real defect, a regression risk you can't accept — the header MUST be Changes Requested or Blocked. Approved with notes is reserved for non-blocking observations only. "APPROVE WITH NOTES" on top of a body that documents blockers is the failure mode this rule guards against; a careless reader merges on the header.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 317 lines · 62 tokens per session scan A cff083d6c982
qa-engineer is a skill published in the GitHub repository MotWakorb/ai-agent-dev-team (2 stars, last pushed 22d ago), licensed MIT. It adds 62 tokens to every session and 5,827 once invoked, about $0.0003 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…