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-audit)<a href="https://agentmods.dev/commands/christopherlouet/claude-base/qa-audit"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/qa-audit/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-audit"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/qa-audit.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.00438 |
| Opus 5.5 | $0.00000 | $0.00175 |
| Sonnet 5.5 | $0.00000 | $0.00088 |
| Haiku 4.5 | $0.00000 | $0.00044 |
Grade A, and why
qa-audit 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.
What it actually says
AUDIT-FULL Agent
Complete project quality audit. Combines security, GDPR, accessibility, performance and code quality.
Context
$ARGUMENTS
Objective
Execute a multi-domain audit and provide a consolidated report with scores, prioritized issues and action plan.
Workflow
- Phase 1: Security Audit (OWASP Top 10, headers, CORS, secrets)
- Phase 2: GDPR Audit (personal data, consent, rights, DPA)
- Phase 3: Accessibility Audit (WCAG 2.1 AA, keyboard, contrast)
- Phase 4: Performance Audit (Core Web Vitals, images, cache, DB)
- Phase 5: Code Quality (linting, tests, coverage, technical debt)
- Consolidate scores and generate the final report
Expected output
Global scores
| Domain | Score /100 | Critical | High |
|---|---|---|---|
| Security | |||
| GDPR | |||
| Accessibility | |||
| Performance | |||
| Quality |
Critical issues (immediate action)
| # | Domain | Issue | Impact | Recommendation |
|---|
Prioritized action plan
- Priority 1 - Critical (this week)
- Priority 2 - High (this month)
- Priority 3 - Medium (this quarter)
Related agents
| Agent | When to use it |
|---|---|
/qa:qa-security |
Deep security audit |
/legal:legal-rgpd |
Deep GDPR audit |
/qa:wcag-audit |
Deep accessibility audit |
/qa:qa-perf |
Deep performance audit |
/ops:ops-health |
Quick check before audit |
IMPORTANT: This audit provides an overview. For a deep audit of a specific domain, use the dedicated agent.
YOU MUST prioritize issues by criticality and provide concrete actions.
NEVER ignore critical security issues - they must be fixed immediately.
Think hard about interdependencies between domains (e.g., security impacts GDPR).
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 · 60 lines · 0 tokens per session scan A de8b90453add
qa-audit is a command published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 438 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
migrate
Generate and manage database migrations.
scaffold
Scaffold project components from templates.
deploy
Deploy application with pre/post-deploy checks.
update-counts
Explicitly refresh public toolkit and committed marketplace source snapshots and numeric documentation.
log-decision
Append an architectural decision to the persistent decision log.
session-log
Explain where session history lives now that the toolkit keeps no session log.