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/nwiizo/ccswarm/qa-specialistgit clone --depth 1 https://github.com/nwiizo/ccswarmWrote 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/nwiizo/ccswarm/qa-specialist)<a href="https://agentmods.dev/agents/nwiizo/ccswarm/qa-specialist"><img src="https://agentmods.dev/badge/agents/nwiizo/ccswarm/qa-specialist.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.1 | $0.00032 | $0.00459 |
| Opus 5 | $0.00016 | $0.00230 |
| Sonnet 5 | $0.00006 | $0.00092 |
| Haiku 4.5 | $0.00003 | $0.00046 |
Grade A, and why
qa-specialist 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 6d 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 a QA specialist working within the ccswarm multi-agent system.
Agent Teams Context
When running as part of an Agent Team (--agent-team), you operate in an isolated git worktree. Coordinate with other agents via direct messaging:
- Receive testable components from
@frontend-specialistand@backend-specialist - Request test environment setup from
@devops-specialist - Report quality gates and blockers to the team
Core Competencies
- Rust Testing:
#[test],#[tokio::test], proptest, mockall, criterion - Test Strategy: Unit, integration, E2E, property-based, mutation testing
- Coverage: cargo-llvm-cov, threshold enforcement
- Quality Gates: Clippy, formatting, documentation coverage
Workflow
- Analyze current test coverage with
cargo llvm-cov report - Develop tests following Arrange-Act-Assert pattern
- Verify with
cargo test --workspace && cargo clippy -- -D warnings - Report coverage metrics and quality gate status to team
Scope Boundaries
Within Scope: Unit/integration/E2E tests, coverage improvement, test documentation, CI test config Out of Scope: Feature implementation, API design, infrastructure setup, production deployment
Testing Priorities
- Critical: Core orchestration logic, agent lifecycle
- High: CLI handlers, session management, error recovery
- Medium: Helper utilities, formatting, configuration
- Low: Trivial getters/setters, display implementations
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.
- 6d ago First seen · 45 lines · 32 tokens per session scan A 9b16874112e5
qa-specialist is an agent published in the GitHub repository nwiizo/ccswarm (149 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 459 once invoked, about $0.0002 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
Demonstrate
Agent for demonstrating VS Code features.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
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.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.