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 skills add jhlee0409/all-for-claudecode --skill qagit clone --depth 1 https://github.com/jhlee0409/all-for-claudecodeWrote 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/skills/jhlee0409/all-for-claudecode/qa)<a href="https://agentmods.dev/skills/jhlee0409/all-for-claudecode/qa"><img src="https://agentmods.dev/badge/skills/jhlee0409/all-for-claudecode/qa/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/skills/jhlee0409/all-for-claudecode/qa"><img src="https://agentmods.dev/badge/skills/jhlee0409/all-for-claudecode/qa.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.00018 | $0.01542 |
| Opus 5 | $0.00009 | $0.00771 |
| Sonnet 5 | $0.00004 | $0.00308 |
| Haiku 4.5 | $0.00002 | $0.00154 |
Grade A, and why
afc:qa scanned grade A with 1 finding 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 9d 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.
Reads agent configuration directorieslowAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
!`cat .claude/afc.config.md 2>/dev/null || echo "[CONFIG NOT FOUND] Proceeding without config — read CLAUDE.md for project info."` Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/afc:qa — Project Quality Audit
Detects quality gaps between structural correctness and actual runtime behavior. Read-only — does not modify any files. Reports findings to console only.
Arguments
$ARGUMENTS— (optional) scope of audit. Defaults toall.all— run all 5 categoriestests— category A only (Test Confidence)errors— category B only (Error Resilience)coverage— categories A + D (Test Confidence + API & Contract Safety)- Or a free-form concern (e.g., "are error messages user-friendly", "check for dead exports")
Project Config (auto-loaded)
!cat .claude/afc.config.md 2>/dev/null || echo "[CONFIG NOT FOUND] Proceeding without config — read CLAUDE.md for project info."
Audit Categories
A. Test Confidence
Evaluate whether the test suite actually catches regressions.
Checks:
- Assertion density: ratio of assertions to test functions (low ratio = weak tests)
- Test-to-code ratio: test LOC vs source LOC per layer (guided by
{config.architecture}) - Mock overuse: tests that mock so much they only test the mock setup
- Runtime verification: execute
{config.test}and analyze output (pass/fail counts, skipped tests, timing) - Missing coverage: source files/modules with zero test coverage
B. Error Resilience
Evaluate whether errors are handled consistently and helpfully.
Checks:
- Catch consistency: unhandled promise rejections, empty catch blocks, swallowed errors
- Error propagation: errors that lose context through the call chain
- User-facing messages: cryptic error strings, raw stack traces exposed to users
- Boundary validation: missing input validation at API/CLI/form boundaries
- Apply
{config.code_style}error handling rules if available
C. Build & CI Integrity
Evaluate whether CI pipeline is healthy and reproducible.
Checks:
- CI execution: run
{config.ci}and{config.gate}commands, verify they pass - Lock file integrity: lock file present, consistent with manifest (package.json vs lock, etc.)
- Unused dependencies: declared but never imported packages
- Build reproducibility: environment-dependent paths, hardcoded secrets, missing env vars
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.
- 9d ago First seen · 178 lines · 18 tokens per session scan A 403761b89497
afc:qa is a skill published in the GitHub repository jhlee0409/all-for-claudecode (7 stars, last pushed 5mo ago), licensed MIT. It adds 18 tokens to every session and 1,542 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
plan-pipeline-execute
Execute a validated plan: worktree isolation, TDD scaffolding, level-based parallel agents, quality gate with smoke test, PR creation and merge. Handles everything through to merged PR.
qa
Systematic QA testing of a web application: diff-aware, tiered, with fix-and-verify loop.
accessibility-a11y
WCAG 2.2 compliance, ARIA patterns, keyboard navigation, screen readers, automated testing.
plan-pipeline-eng-review
Engineering architecture gate: lock architecture, diagrams, edge cases, and test matrix before writing implementation code.
ci-all
Full CI pipeline: run local tests, type check, push branch, and return the pipeline URL. The only command you need before opening a PR.
generate-tests
Generate comprehensive tests for specified code.