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/agents/christopherlouet/claude-base/qa-loop)<a href="https://agentmods.dev/agents/christopherlouet/claude-base/qa-loop"><img src="https://agentmods.dev/badge/agents/christopherlouet/claude-base/qa-loop/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/agents/christopherlouet/claude-base/qa-loop"><img src="https://agentmods.dev/badge/agents/christopherlouet/claude-base/qa-loop.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.00072 | $0.02770 |
| Opus 5.5 | $0.00029 | $0.01108 |
| Sonnet 5.5 | $0.00014 | $0.00554 |
| Haiku 4.5 | $0.00007 | $0.00277 |
Grade A, and why
qa-loop 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 1mo 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 — 256 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent QA-LOOP
Autonomous AUDIT (parallel) → VALIDATE → FIX → VERIFY → CHECK loop with stop criteria.
Adopts the Anthropic 2026 pattern (official code-review plugin): parallelization, false positive validation, high-signal filter, auto-scope.
Global workflow
┌────────────────────────────────────────────────────────────────────────┐
│ QA-LOOP (v2) │
│ │
│ ┌──────────────┐ ┌──────────┐ ┌─────────┐ ┌──────────┐ │
│ │ AUDIT │──→│ VALIDATE │──→│ FIX │──→│ VERIFY │ │
│ │ 4 sub-agents │ │ 1 per │ │ P0 then │ │ tests │ │
│ │ in parallel │ │ finding │ │ P1 │ │ lint │ │
│ └──────────────┘ └──────────┘ └─────────┘ └──────────┘ │
│ ↑ │ │
│ │ ┌──────────┐ │ │
│ └──────────────│ CHECK │←─────────────────────┘ │
│ │ stop │ │
│ │ criteria │ │
│ └──────────┘ │
│ │ │
│ score >= target AND 0 P0/P1 ? │
│ │ │
│ YES: STOP │
│ NO: LOOP (back to AUDIT) │
└────────────────────────────────────────────────────────────────────────┘
Parameters
| Parameter | Default | Description |
|---|---|---|
| Target score | 90/100 | Minimum score to stop the loop |
| Max iterations | 5 | Maximum number of audit-fix cycles |
| Domains | all | security, perf, a11y, claudemd (4 sub-agents) |
| Fix severity | P0+P1 | Only fix validated high-signal issues |
| Scope | git diff main...HEAD |
Audit limited to files modified on the branch |
--audit-only |
off | Read-only mode: audit + report, no FIX |
--comment |
off | Post inline on the current PR via gh pr comment |
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.
- 1mo ago First seen · 256 lines · 72 tokens per session scan A b737709018aa
qa-loop is an agent published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed 4d ago), licensed MIT. It adds 72 tokens to every session and 2,770 once invoked, about $0.0003 per session on Opus 5.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-31.
Other agents, from other repositories
refuter-regression
Breaks a diff on regression — anything that worked before this change and doesn't now, including quietly weakened checks. Read-only, re-runs the pass-to-pass suite itself. Invoked only by mnm-verify; never by the user, never by the implementer.
gsd-verifier
Verifies phase goal achievement through goal-backward analysis. Checks codebase delivers what phase promised, not just that tasks completed. Creates VERIFICATION.md report.
solid-isp-dip-judge
Evaluates code implementation adherence to SOLID Interface Segregation Principle (ISP) and Dependency Inversion Principle (DIP).
test-judge
Evaluates test content quality including coverage, assertions, structure, and best practices.
e2e-test-specialist
Playwright, Cypress, and visual regression testing specialist. Use when writing E2E tests, setting up browser automation, or implementing visual regression testing. Trigger phrases: E2E, end-to-end, Playwright, Cypress, visual regression, browser test, screenshot test, Percy, Chromatic.
verification-subagent
Verifies if a task from the implementation plan has been completed by checking source files.