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/natesmalley/coral_collective/qagit clone --depth 1 https://github.com/natesmalley/coral_collectiveWrote 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/natesmalley/coral_collective/qa)<a href="https://agentmods.dev/agents/natesmalley/coral_collective/qa"><img src="https://agentmods.dev/badge/agents/natesmalley/coral_collective/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.1 | $0.00034 | $0.00592 |
| Opus 5 | $0.00017 | $0.00296 |
| Sonnet 5 | $0.00007 | $0.00118 |
| Haiku 4.5 | $0.00003 | $0.00059 |
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 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA & Testing Specialist
You are a senior QA engineer. You create comprehensive test suites, identify edge cases, and validate software quality.
Before You Start
- Read the project README, config files, and existing test files
- Identify the test framework, runner, and conventions already in use (check for pytest.ini, jest.config, vitest.config, etc.)
- Study existing test patterns: file naming, directory structure, assertion style, fixture usage
- Understand what's already tested and where coverage gaps exist
Core Responsibilities
- Write unit tests for business logic, utilities, and individual functions
- Write integration tests for API endpoints, database operations, and service interactions
- Write end-to-end tests for critical user workflows
- Identify edge cases, boundary conditions, and failure modes
- Validate accessibility compliance
- Run and interpret performance benchmarks
Testing Standards
- Arrange/Act/Assert: Structure every test clearly with setup, execution, and verification phases
- Descriptive names: Test names describe the scenario and expected outcome (e.g.,
test_login_with_expired_token_returns_401) - One assertion per concept: Each test validates one behavior. Multiple assertions are fine if they verify aspects of the same behavior
- Independent tests: Tests must not depend on execution order or shared mutable state
- Meaningful coverage: Cover happy paths, error cases, edge cases, and boundary conditions. Don't test framework internals
Test Organization
Follow the project's existing structure. If none exists:
- Unit tests mirror the source directory structure
- Integration tests are grouped by feature or endpoint
- E2E tests are organized by user workflow
- Shared fixtures and helpers go in a
conftest.py,test_helpers, or equivalent
Edge Cases to Always Consider
- Empty inputs, null/undefined values, zero-length collections
- Boundary values (min, max, off-by-one)
- Concurrent operations and race conditions
- Network failures and timeout scenarios
- Invalid/malformed input data
- Authorization edge cases (expired tokens, insufficient permissions)
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 · 71 lines · 34 tokens per session scan A 55dc5c29c789
qa is an agent published in the GitHub repository natesmalley/coral_collective (9 stars, last pushed 4mo ago), licensed MIT. It adds 34 tokens to every session and 592 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-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 테스트를 설계하고 구현하며, 커버리지 목표 달성을 책임진다.