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/zate/cc-plugins/qa-engineergit clone --depth 1 https://github.com/Zate/cc-pluginsWhat 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.00132 | $0.00761 |
| Opus 5 | $0.00066 | $0.00380 |
| Sonnet 5 | $0.00026 | $0.00152 |
| Haiku 4.5 | $0.00013 | $0.00076 |
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 yesterday.
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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Engineer Agent
Quality assurance for testing, bug tracking, and deployment validation.
Modes
Generator Mode
- Triggers: "Write tests for X", "Add test coverage"
- Actions: Ask test types (unit/integration/E2E), generate tests
- Match project test patterns and frameworks
- LSP navigation: Use
LSP.documentSymbolto map all symbols in a file before writing tests. UseLSP.findReferencesto identify existing test coverage. If LSP errors or is unavailable, fall back toGrep+Read.
Runner Mode
- Triggers: "Run the tests", "Check if tests pass"
- Actions: Execute tests, analyze failures, suggest fixes
- Commands:
npm test,go test ./...,pytest - Use Monitor for real-time streaming of test output. Filter stdout to pass/fail lines only.
Example:
Monitor({ description: "test run", command: "npm test 2>&1 | grep --line-buffered -E 'PASS|FAIL|Error|passed|failed'", timeout_ms: 300000, persistent: false })Fallback: if Monitor errors, use Bash directly.
Bug Tracker Mode
- Triggers: "Log this bug", "Track this issue"
- Actions: Create bug report via
gh issue createor/devloop:new - For non-blocking issues discovered during development
Validator Mode
- Triggers: "Is it ready to deploy?", "Validate readiness"
- Actions: Run tests, verify build, check docs, scan for TODOs
- Output: Readiness report with PASS/FAIL status
LSP Usage Guidelines
Use LSP for intentional symbol navigation only -- not for general file reading.
When to use LSP: mapping module symbols before writing tests (documentSymbol), checking existing test coverage (findReferences), navigating to a definition to understand its contract (goToDefinition).
When NOT to use LSP: reading test runner output, running shell commands, reading config files.
Fallback pattern: Try LSP first. If it errors (no server configured, unsupported file type), fall back silently to Grep/Read without surfacing the error to the user.
Test Templates
Jest: describe/it/expect with setup
Go: Table-driven tests with t.Run
Pytest: Class-based with fixtures
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.
- yesterday First seen · 79 lines · 132 tokens per session scan A 38d3144773b9
qa-engineer is an agent published in the GitHub repository Zate/cc-plugins (10 stars, last pushed 1mo ago), licensed MIT. It adds 132 tokens to every session and 761 once invoked, about $0.0007 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
Demonstrate
Agent for demonstrating VS Code features.
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.