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/Qualimetry/claude-code-qualimetry-ai-appWrote 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/qualimetry/claude-code-qualimetry-ai-app/compliance-pull)<a href="https://agentmods.dev/commands/qualimetry/claude-code-qualimetry-ai-app/compliance-pull"><img src="https://agentmods.dev/badge/commands/qualimetry/claude-code-qualimetry-ai-app/compliance-pull/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/qualimetry/claude-code-qualimetry-ai-app/compliance-pull"><img src="https://agentmods.dev/badge/commands/qualimetry/claude-code-qualimetry-ai-app/compliance-pull.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.00210 |
| Opus 5.5 | $0.00007 | $0.00084 |
| Sonnet 5.5 | $0.00004 | $0.00042 |
| Haiku 4.5 | $0.00002 | $0.00021 |
Grade A, and why
compliance-pull 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
Compliance: Pull
Force a fresh fetch of review findings for the target file, bypassing any per-session cache the on-Read hook may have populated.
- Resolve the target file the same way
/compliance-checkdoes. - Delete the cache entry for this file at
$TMPDIR/qualimetry-ai-app-cache/<repo>/<branch>/<file>.json(if present). - Invoke the bundled
review-checkskill on the file (which always hits the MCP; the cache is only used by the on-Read hook). - Show the findings as
/compliance-checkwould.
Use this when a fresh review has just landed server-side and you want to see the new findings immediately rather than waiting for the cache TTL (30 minutes) to expire.
If the MCP isn't configured, emit the verbatim self-healing message from /compliance-check.
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 · 18 lines · 18 tokens per session scan A 964287e84a8a
compliance-pull is a command published in the GitHub repository Qualimetry/claude-code-qualimetry-ai-app (1 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 18 tokens to every session and 210 once invoked, about $0.0001 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 commands, from other repositories
code-review-teach
Educational code review that teaches while reviewing. Provides constructive feedback, explains best practices, discusses trade-offs, and helps developers improve their coding skills.
hidden-dependencies
Discover hidden dependencies, implicit contracts, and non-obvious couplings in the codebase.
dead-code-scan
Scan for dead code, unused imports, duplicates, and zombie code across the project.
dead-code-clean
Actively find and remove dead code, unused imports, duplicates, and zombie code.
esp-teach
One-time project setup -- discover hardware, find datasheets, persist context to CLAUDE.md.
swift-critique
Critique SwiftUI code for patterns, design, clean code, accessibility, and performance.