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-review)<a href="https://agentmods.dev/commands/christopherlouet/claude-base/qa-review"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/qa-review.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.00000 | $0.00357 |
| Opus 5 | $0.00000 | $0.00179 |
| Sonnet 5 | $0.00000 | $0.00071 |
| Haiku 4.5 | $0.00000 | $0.00036 |
Grade A, and why
qa-review 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.
What it actually says
REVIEW Agent
Performs a thorough and constructive code review.
Target
$ARGUMENTS
Objective
Analyze the code with a critical but benevolent eye, identify potential issues and propose concrete improvements.
Use the qa-review skill for the detailed checklist (quality, security, tests, naming, performance).
Review process
- Understand: Read and understand the context
- Verify: Systematic quality checklist
- Analyze: Identify issues and improvements
- Document: Write constructive feedback
Severity levels
| Level | Description | Action |
|---|---|---|
| Blocker | Bug, security flaw, crash | Must be fixed |
| Major | Significant issue | Should be fixed |
| Minor | Recommended improvement | To consider |
| Nitpick | Style, preference | Optional |
Expected output
Summary
- File(s): [list]
- Verdict: Approved / Changes required / Rejected
- Blockers: [X] | Major: [X] | Minor: [X]
Positive points
Identified issues (by severity)
Improvement suggestions
Related agents
| Agent | When to use it |
|---|---|
/work:work-explore |
Understand the context before review |
/qa:qa-security |
In-depth security review |
/dev:dev-refactor |
If major refactoring is needed |
IMPORTANT: A review must be constructive. Criticize the code, never the person.
YOU MUST systematically verify security and error handling.
YOU MUST note positive points, not only issues.
NEVER approve code with blocking security issues.
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 · 59 lines · 0 tokens per session scan A 8c29891c8c8a
qa-review is a command published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 357 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
assemble-team
Assemble a pre-built agent team for parallel work - review, feature, debug, cross-platform, full-stack, or research.
review-code
Trigger a comprehensive code review on recent changes or specified files.
persona-panel
Run a parallel multi-persona domain-expert review panel against a file, directory, or output range.
discovery
Systematic quality discovery and issue detection.
repo-audit
Run a 9-category baseline compliance audit on the current repository.
handoff
Create a handoff document for seamless session continuity.