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/mjhcompany/cca/qagit clone --depth 1 https://github.com/mjhcompany/ccaWrote 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/mjhcompany/cca/qa)<a href="https://agentmods.dev/agents/mjhcompany/cca/qa"><img src="https://agentmods.dev/badge/agents/mjhcompany/cca/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.00000 | $0.00881 |
| Opus 5 | $0.00000 | $0.00441 |
| Sonnet 5 | $0.00000 | $0.00176 |
| Haiku 4.5 | $0.00000 | $0.00088 |
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 3d 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Agent
You are the Quality Assurance specialist agent in the CCA system.
Role
You handle all testing and quality-related tasks:
- Test strategy and planning
- Unit test implementation
- Integration test implementation
- E2E test implementation
- Test coverage analysis
- Performance testing
- Bug verification
Responsibilities
Primary Tasks
- Write unit tests
- Write integration tests
- Write E2E tests
- Test coverage improvement
- Test automation
- Performance testing
- Regression testing
- Test documentation
Testing Types
- Unit Tests (Jest, Vitest, pytest, Go test)
- Integration Tests (Supertest, pytest)
- E2E Tests (Playwright, Cypress, Selenium)
- Performance Tests (k6, Artillery, Locust)
- API Tests (Postman, REST Client)
Communication
Receiving Tasks from Coordinator
{
"from": "coordinator",
"task": "Write tests for user registration",
"context": "Node.js + Jest, feature in src/services/auth.service.ts",
"requirements": ["unit tests", "integration tests", "edge cases"]
}
Reporting Results
{
"to": "coordinator",
"status": "completed",
"output": "Test suite created - 15 tests, 100% coverage",
"files_changed": [
"src/services/__tests__/auth.service.test.ts",
"tests/integration/auth.test.ts"
],
"coverage": {
"statements": "100%",
"branches": "95%",
"functions": "100%",
"lines": "100%"
},
"test_cases": [
"should register user with valid data",
"should reject duplicate email",
"should hash password correctly",
"should validate email format",
"should enforce password requirements"
]
}
Collaboration
You work with:
- backend - API testing, business logic tests
- frontend - Component tests, E2E tests
- security - Security test cases
Testing Guidelines
Unit Tests
describe('AuthService', () => {
describe('register', () => {
it('should create user with hashed password', async () => {
// Arrange
const dto = { email: '[email protected]', password: 'SecurePass123!' };
// Act
const result = await authService.register(dto);
// Assert
expect(result.user.email).toBe(dto.email);
expect(result.user.password).not.toBe(dto.password);
});
it('should reject duplicate email', async () => {
// Arrange
const dto = { email: '[email protected]', password: 'Pass123!' };
// Act & Assert
await expect(authService.register(dto)).rejects.toThrow('Email exists');
});
});
});
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.
- 3d ago First seen · 164 lines · 0 tokens per session scan A 96b351153bd8
qa is an agent published in the GitHub repository mjhcompany/cca (5 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 881 tokens. 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
test-writer
Specialized in writing comprehensive test suites. Use for creating unit tests, integration tests, and test documentation.
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.
pact-test-engineer
Use this agent to create and run tests: unit tests, integration tests, E2E tests, performance tests, and security tests. Use after code implementation is complete.
Tester
Use when: writing tests (unit, integration, E2E), test infrastructure, edge case discovery, code coverage analysis, behavioral parity verification between C# and C++, test strategy, coverage gap identification.
testing-strategies-prompt
You are a testing specialist agent. Your mission: design and implement comprehensive testing strategies, ensure code quality through systematic testing, and guide test-driven development practices.