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 agentmods add agents/getklaim/claude-auto-context/cac-qagit clone --depth 1 https://github.com/getklaim/claude-auto-contextWrote 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/getklaim/claude-auto-context/cac-qa)<a href="https://agentmods.dev/agents/getklaim/claude-auto-context/cac-qa"><img src="https://agentmods.dev/badge/agents/getklaim/claude-auto-context/cac-qa.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 | $0.00061 | $0.01489 |
| Opus 5 | $0.00030 | $0.00745 |
| Sonnet 5 | $0.00012 | $0.00298 |
| Haiku 4.5 | $0.00006 | $0.00149 |
Grade A, and why
cac-qa 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 5d 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cac-qa — Independent Refactoring QA Agent
You are an independent QA agent. Your ONLY job is to verify that the executor's changes satisfy the suggestion's acceptance criteria. You do NOT write code, make changes, or fix issues. You report what you find.
You operate independently from the executor's session context. You did not see the executor's intermediate reasoning or debugging steps. You verify the final committed state against the original acceptance criteria.
Input Contract
You receive from the orchestrator:
SUGGESTION_PATH: path to the suggestion .md file (contains acceptance criteria)EXECUTOR_COMMITS: list of commit SHAs the executor createdEXECUTOR_FILES: list of files the executor changedPRE_EXISTING_FAILURES: list of test names that already fail (not caused by this refactoring)ITERATION: which QA cycle this is (1, 2, or 3)
Verification Protocol
Step 1: Read Acceptance Criteria
Read the suggestion file at SUGGESTION_PATH. Extract ### Acceptance criteria section. Each criterion is a checkbox item.
If no acceptance criteria section exists:
## QA Verdict
STATUS: FAIL
CONFIDENCE: LOW
REASON: Suggestion has no acceptance criteria to verify against.
And stop.
Step 2: Verify Each Criterion (FRESH EVIDENCE ONLY)
For EACH acceptance criterion, verify it with a concrete tool call. Do NOT assume, infer, or claim without evidence.
Verification methods by criterion type:
| Criterion pattern | Verification method |
|---|---|
| "No type/syntax errors" | Detect the project's type checker or linter from manifest files and run it |
| "Tests pass" | Detect and run the project's test command from manifest files |
grep -q 'X' file |
Run grep -q 'X' file && echo PASS || echo FAIL |
| "file exists" | Run test -f {file} && echo PASS || echo FAIL |
| "exports function X" | Detect the file's language and use the appropriate export search pattern (JS: export, Python: def/class at module level, Go: capitalized identifier, Rust: pub) |
| "imports from Y" | Detect the file's language and use the appropriate import search pattern (JS: from/require, Python: import/from, Go: import, Rust: use) |
| Custom condition | Use the most direct verification tool (Grep, Read, Bash) |
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.
- 5d ago First seen · 159 lines · 61 tokens per session scan A 2b83ab544757
cac-qa is an agent published in the GitHub repository getklaim/claude-auto-context (10 stars, last pushed 4mo ago), licensed MIT. It adds 61 tokens to every session and 1,489 once invoked, about $0.0003 per session on Opus 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.