A command that audits project artifacts—such as agents, skills, and related files—for quality, completeness, effectiveness, and alignment with their templates.

Use it to inventory and review artifacts in build repositories or project-specific folders, with separate checks for quality and template synchronization.

It finds missing, weak, or misplaced project materials and checks whether they follow the repository's expected structure.

cc-audit — Command for Claude Code by terrene-foundation

Install

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.

Clone the repo

git clone --depth 1 https://github.com/terrene-foundation/kailash-coc-claude-py

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/terrene-foundation/kailash-coc-claude-py/cc-audit/github.svg)](https://agentmods.dev/commands/terrene-foundation/kailash-coc-claude-py/cc-audit)

Your own site

<a href="https://agentmods.dev/commands/terrene-foundation/kailash-coc-claude-py/cc-audit"><img src="https://agentmods.dev/badge/commands/terrene-foundation/kailash-coc-claude-py/cc-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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/terrene-foundation/kailash-coc-claude-py/cc-audit"><img src="https://agentmods.dev/badge/commands/terrene-foundation/kailash-coc-claude-py/cc-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 617 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00617
Opus 5	$0.00009	$0.00309
Sonnet 5	$0.00003	$0.00123
Haiku 4.5	$0.00002	$0.00062

Measured 8d ago against content hash 883ea2c56e9d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

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 8d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

cc-audit — 89% identical, 6 lines differ

.claude/commands/cc-audit.md · 52 lines

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, the Rust SDK, kailash-prism): no agents/project/ or skills/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 just project/.
Downstream USE repos (consumer projects): project-specific artifacts live in agents/project/ and skills/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/ and skills/project/ should not exist.
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-from-template.

Read the full file on GitHub · 52 lines

Changes

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.

8d ago First seen · 52 lines · 17 tokens per session scan A 883ea2c56e9d

Subscribe to this mod's changes

cc-audit is a command published in the GitHub repository terrene-foundation/kailash-coc-claude-py (12 stars, last pushed 24d ago), licensed Apache-2.0. It adds 17 tokens to every session and 617 once invoked, about $0.0001 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-09-03.

Code review Project management

cc-audit

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

Copies of this mod

How it starts

CC Artifact Audit (Project)

BUILD vs USE Repo Distinction

Your Role

Phase 1: Fidelity Audit

Phase 2: Template Alignment

What this file has done since we first saw it

Other commands, from other repositories

gh-triage

sync-pr-dashboard

discover

migrate

exception

backlog