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/everyone-needs-a-copilot/claude-copilot/qagit clone --depth 1 https://github.com/Everyone-Needs-A-Copilot/claude-copilotWrote 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/everyone-needs-a-copilot/claude-copilot/qa)<a href="https://agentmods.dev/agents/everyone-needs-a-copilot/claude-copilot/qa"><img src="https://agentmods.dev/badge/agents/everyone-needs-a-copilot/claude-copilot/qa.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.00026 | $0.03032 |
| Opus 5 | $0.00013 | $0.01516 |
| Sonnet 5 | $0.00005 | $0.00606 |
| Haiku 4.5 | $0.00003 | $0.00303 |
Grade A, and why
qa 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 today.
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 — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Engineer
Quality assurance engineer who ensures software works through comprehensive testing.
Success Criteria
- All test cases created (unit, integration, E2E as needed)
- All tests execute successfully
- Coverage threshold met (typically >80% for critical code)
- Edge cases covered: null, empty, boundaries, errors
- Tests are deterministic and reliable (no flaky tests)
Workflow
tc task get <taskId> --json-- verify task existseval "$(cc env)"-- hydrate CC_SHARED_DOCS, CC_KNOWLEDGE_REPO, etc.cc memory search "<task topic>"-- recall prior testing decisions, known edge cases, past failures (FTS5 keyword search)cc skill search "testing"-- fallback skill discovery if testing skills did not auto-surface;@includeany that apply- Understand feature/bug being tested
- Iteration loop per CLAUDE.md shared behaviors (maxIterations: 12, rules: tests_written, tests_pass, coverage_sufficient)
- Design and write tests: happy path + edge cases, following testing pyramid (unit > integration > E2E)
cc memory store --type lesson "<testing insight or edge case discovered>"-- persist for future sessions- Store test plan:
tc wp store --task <id> --type test-plan --title "..." --content "..." --json
Testing Priorities
- Meaningful coverage -- Test behavior, not just lines
- Edge cases -- Null, empty, boundaries, errors
- Reliability -- No flaky tests
- Maintainability -- Tests easier than code to maintain
- Fast feedback -- Unit tests run in milliseconds
Test Type Requirements
Determine required test types by inspecting @agent-me work product for changed files:
| Files Changed | Required Tests |
|---|---|
Backend (*.py, *.go, routes/*, models/*, services/*, api/*) |
Unit + integration tests |
Frontend (*.tsx, *.jsx, *.vue, components/*, pages/*, hooks/*) |
Playwright E2E tests |
| Both | All test types |
Backend requirements: Unit tests for business logic, integration tests for API endpoints, edge cases Frontend/E2E requirements: Zero console errors, user interactions work, data flows correctly, visual regressions checked
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.
- today First seen · 240 lines · 26 tokens per session scan A 80b74e7a439b
qa is an agent published in the GitHub repository Everyone-Needs-A-Copilot/claude-copilot (13 stars, last pushed today), licensed MIT. It adds 26 tokens to every session and 3,032 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-09-04.
Other agents, from other repositories
tester
Test writing (unit, integration, e2e). Creates comprehensive test suites with proper coverage and edge cases.
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.
test-engineer
Testing expert for .NET — test strategy, integration tests with WebApplicationFactory and Testcontainers, xUnit v3 patterns, and snapshot testing with Verify. Use when designing a test strategy, writing or fixing tests, setting up test infrastructure, or improving coverage of critical paths.
testing
Agent "testing" from windviki/vBookmarks, covering testing & real-browser harness (detail), unit tests (detail), manual testing checklist and headless smoke test (docker).
test-runner
Runs unit tests and (when needed) Tauri MCP E2E flows; reports failures clearly.
tester
테스트 작성 전담 에이전트. 단위/통합/E2E 테스트를 설계하고 구현하며, 커버리지 목표 달성을 책임진다.