setup-audit

A command for checking and improving a Claude Code toolkit's configuration. It includes full, quick, security, optimization, consolidation, and migration modes.

In plain words
What is it for?
Use it to audit the configuration, run a security check, apply improvements, merge similar components, or copy existing Claude configuration into the toolkit.
Why use it?
It helps reveal security or coverage problems and gives you a structured way to improve the setup.

Command

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.

agentmods
npx agentmods add commands/hknc/claude-evolve/setup-audit
Clone the repo
git clone --depth 1 https://github.com/hknc/claude-evolve
Per session 50 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 279 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00050 $0.00279
Opus 5 $0.00025 $0.00139
Sonnet 5 $0.00010 $0.00056
Haiku 4.5 $0.00005 $0.00028

Measured 2d ago against content hash 80c880628bf1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

setup-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 2d 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.

plugins/claude-evolve/commands/setup-audit.md · 37 lines

What it actually says

/setup-audit Command

This is an alias for /evolve audit. Prefer /evolve audit for consistency.

Action

Invoke the claude-evolve:evolve-setup-auditor agent via Task tool.

Execution

  1. Parse mode from arguments (default: full)
  2. Spawn claude-evolve:evolve-setup-auditor agent with mode parameter
  3. Return audit results to user

Modes

Mode Action
full Run complete audit (security + coverage + recommendations)
quick Fast security and coverage check
security Deep security analysis
optimize Apply pending improvements to toolkit
consolidate Merge similar components
migrate Copy $HOME/.claude/ content to toolkit

Prerequisite

Check that toolkit is initialized ($HOME/.claude-evolve/active exists). If not, tell user to run /evolve init first.

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.

  1. 2d ago First seen · 37 lines · 50 tokens per session scan A 80c880628bf1

Subscribe to this mod's changes

setup-audit is a command published in the GitHub repository hknc/claude-evolve (8 stars, last pushed 7mo ago), licensed MIT. It adds 50 tokens to every session and 279 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.