Borrowing it
Nothing to install: this file belongs to terrene-foundation/metis. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/terrene-foundation/metis/main/.claude/commands/cc-audit.mdgit clone --depth 1 https://github.com/terrene-foundation/metisWrote 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/terrene-foundation/metis/cc-audit)<a href="https://agentmods.dev/commands/terrene-foundation/metis/cc-audit"><img src="https://agentmods.dev/badge/commands/terrene-foundation/metis/cc-audit.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.00017 | $0.00614 |
| Opus 5 | $0.00009 | $0.00307 |
| Sonnet 5 | $0.00003 | $0.00123 |
| Haiku 4.5 | $0.00002 | $0.00061 |
Grade A, and why
cc-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 7d 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.
This is a copy
89% identical to cc-audit — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CC Artifact Audit (Project)
Reviews your repo's artifacts for quality and template alignment. Scope depends on repo type.
BUILD vs USE Repo Distinction
- BUILD repos (kailash-py, kailash-rs, kailash-prism): no
agents/project/orskills/project/directories. Every artifact lives in a canonical location (agents/frameworks/,skills/01-core-sdk/, etc.) and is subject to the same fidelity checks as loom/. The Phase 1 inventory in a BUILD repo walks ALL artifact directories, not justproject/. - Downstream USE repos (consumer projects): project-specific artifacts live in
agents/project/andskills/project/. The Phase 1 inventory focuses on these, since shared artifacts are owned by the upstream template and audited at loom/.
If this repo is a BUILD repo, skip the project/-only inventory below and audit all canonical artifact directories.
Your Role
Specify scope: all, fidelity (quality only), sync (template alignment only), or a specific file/type.
Phase 1: Fidelity Audit
-
Inventory:
- USE repos: list project-specific artifacts (
agents/project/,skills/project/) with line counts. - BUILD repos: list all canonical artifacts (
agents/**/*.md,skills/**/*,rules/*.md,commands/*.md) with line counts;agents/project/andskills/project/should not exist.
- USE repos: list project-specific artifacts (
-
Four-dimension audit per artifact:
- Competency: Precise instructions? Knows its domain?
- Completeness: Edge cases? Missing handoffs?
- Effectiveness: Reliable behavior? Output format specified?
- Token Efficiency: Lean? No redundancy?
-
Hard limits (cc-artifacts rules):
- Agent descriptions under 120 chars with trigger phrases
- Agents under 400 lines, commands under 150 lines
- CLAUDE.md under 200 lines
- Rules have DO/DO NOT examples and Why rationale
-
Cross-reference check: Every referenced artifact exists on disk.
Phase 2: Template Alignment
- Freshness: Check
.coc-sync-marker— when was the last sync from the upstream template? If stale, recommend running/sync.
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.
- 7d ago First seen · 52 lines · 17 tokens per session scan A d8e90d173b33
cc-audit is a command published in the GitHub repository terrene-foundation/metis (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 17 tokens to every session and 614 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to cc-audit, differing in 6 lines, and is treated as a copy.
Other commands, from other repositories
sdd-init
Initialize SDD context — detects project stack and bootstraps persistence backend.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
init
Install the formatters this repository needs, with every command visible before it runs.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
review-sdk-app
Review and validate a Claude Agent SDK application against best practices.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.