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.
git clone --depth 1 https://github.com/christopherlouet/claude-baseWrote 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/commands/christopherlouet/claude-base/qa-automation)<a href="https://agentmods.dev/commands/christopherlouet/claude-base/qa-automation"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/qa-automation/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/christopherlouet/claude-base/qa-automation"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/qa-automation.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.00346 |
| Opus 5 | $0.00000 | $0.00173 |
| Sonnet 5 | $0.00000 | $0.00069 |
| Haiku 4.5 | $0.00000 | $0.00035 |
Grade A, and why
qa-automation 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 7d 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
QA-AUTOMATION Agent
Set up a comprehensive test automation strategy.
Context
$ARGUMENTS
Objective
Automate tests at all levels (unit, integration, E2E) to ensure quality and accelerate release cycles.
Workflow
- Evaluate current coverage and test pyramid
- Configure unit test framework (Vitest/Jest/Pytest)
- Configure integration tests (Supertest, test containers)
- Configure E2E tests (Playwright recommended)
- Set up mocking (MSW)
- Integrate into CI/CD pipeline (GitHub Actions)
- Define quality metrics and thresholds
Expected output
Test pyramid
- Unit (70-80%): framework, coverage config
- Integration (15-25%): API, DB, services
- E2E (5-10%): critical user journeys
CI/CD configuration
- Pipeline with parallelized tests
- Coverage reports and artifacts
Metrics
| Metric | Target |
|---|---|
| Coverage | > 80% |
| Passing tests | 100% |
| Execution time | < 10 min |
| Flaky tests | 0 |
Related agents
| Agent | Usage |
|---|---|
/dev:dev-tdd |
TDD cycle + test infra setup |
/ops:ops-ci |
CI/CD pipeline |
/qa:qa-perf |
Performance tests |
IMPORTANT: Maintain the test pyramid - more unit tests than E2E.
YOU MUST use stable data-testid for E2E tests.
NEVER have interdependent tests - each test must be isolated.
Think hard about the effort/value ratio before automating a scenario.
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.
- 7d ago First seen · 58 lines · 0 tokens per session scan A 4aa4cf2015ce
qa-automation is a command published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 346 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-09-03.
Other commands, from other repositories
test-suite
Run comprehensive test suite with coverage analysis.
test
Agentic end-to-end test orchestrator — drive web/macOS flows, evaluate UX rubric, reconcile issues.
frontend-e2e
Perform a thorough live E2E test of a frontend web application using browser-bridge MCP tools. Tests every page, interactive element, form, navigation flow, responsive breakpoint, and accessibility rule through real browser interaction.
run-all-tests-and-fix
Execute the full test suite and systematically fix any failures, ensuring code quality and functionality.
test-gen
Generate comprehensive tests for a specified file with edge cases and error scenarios.
tester
Comprehensive testing with parallel execution capabilities.