rig-audit

rig-audit is a command for Claude Code from Ertinox7711/SGRR-AGI-V2. It costs 30 tokens per session (843 once invoked), scanned A, original, MIT.

A report-only command that examines how a person works in coding-agent sessions and project folders, then proposes prioritized improvements to their setup. The setup includes instructions, rules, memory, commands, scripts, and settings.

In plain words
What is it for?
Use it to audit a coding-agent setup, compare actual working habits with the installed configuration, and plan upgrades to its rules, memory, commands, hooks, or settings.
Why use it?
It helps reveal gaps and inconsistencies in an existing agent configuration without changing anything automatically. The developer can review the recommendations before applying them.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths; mentions CLAUDE.md.

Good fit Use it to audit a coding-agent setup, compare actual working habits with the installed configuration, and plan upgrades to its rules, memory, commands, hooks, or settings.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/ertinox7711/sgrr-agi-v2/rig-audit
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/Ertinox7711/SGRR-AGI-V2

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.

agentmods badge for rig-audit

README.md
[![agentmods](https://agentmods.dev/badge/commands/ertinox7711/sgrr-agi-v2/rig-audit/github.svg)](https://agentmods.dev/commands/ertinox7711/sgrr-agi-v2/rig-audit)
Your own site
<a href="https://agentmods.dev/commands/ertinox7711/sgrr-agi-v2/rig-audit"><img src="https://agentmods.dev/badge/commands/ertinox7711/sgrr-agi-v2/rig-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.

agentmods 80×15 button for rig-audit

Your own site · 80×15
<a href="https://agentmods.dev/commands/ertinox7711/sgrr-agi-v2/rig-audit"><img src="https://agentmods.dev/badge/commands/ertinox7711/sgrr-agi-v2/rig-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 30 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 843 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00030 $0.00843
Opus 5 $0.00015 $0.00421
Sonnet 5 $0.00006 $0.00169
Haiku 4.5 $0.00003 $0.00084

Measured 11d ago against content hash 4f2ce1818e40, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

rig-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 11d 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.

commands/rig-audit.md · 62 lines

How it starts

The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are running the SGRR AGI V2 self-audit. Goal: study how this user actually works, compare it to what the rig currently provides, and produce a prioritized proposal of upgrades.

This run is report-only. You MUST NOT modify settings, CLAUDE.md, memory, rules, commands, hooks, or any file. Propose; let the user choose what to apply.

Optional focus from the user: $ARGUMENTS (if empty, audit everything).

Work through these five steps, then output the report.

1. Read the current rig

Read what is actually installed under the user's ~/.claude (Windows: $env:USERPROFILE\.claude):

  • settings.json — model, env, permissions, hooks, enabledPlugins, effortLevel
  • CLAUDE.md — behavioral philosophy
  • rules/*.md — lazy per-project rules and their paths:
  • memory/MEMORY.md + memory files
  • commands/*.md — existing slash commands
  • scripts/* — existing hooks

Build a model of what the rig CAN do today.

2. Sample real usage (do NOT ingest everything)

Session transcripts live in ~/.claude/projects/<encoded-path>/*.jsonl (one JSON object per line, files can be huge). Sample, don't load whole files — list the dirs, pick a handful of recent/large transcripts, read only their first and last slices. Extract signal only:

  • recurring intents / task types the user asks for
  • tools and skills used most (and ones never used)
  • friction: repeated corrections, retries, the same thing explained twice, dead ends

Never copy secrets, tokens, emails, or private project content into your output. Summarize patterns, not raw data.

3. Scan the project folders

For each working directory (see additionalDirectories in settings, plus the cwd), survey:

  • languages / frameworks / tooling in use
  • candidate paths: rules that don't exist yet
  • commands the user runs by hand repeatedly (build, test, deploy) that could be a slash command or a hook

4. Cross-reference and find the gaps

Compare step 1 against steps 2+3. Look for:

  • missing rules — a project worked on often with no rules/ entry
  • missing memory — facts re-explained across sessions that should be persisted
  • missing commands — a repeated multi-step flow worth a /command
  • useful skills/plugins not enabled
  • settings drift — permissions too tight or too loose, model/effort mismatch, a hook that never fires
  • stale references — a rule/memory naming a file/flag that no longer exists (verify before flagging)
  • new hook opportunities — a check the user always does by hand

Read the full file on GitHub · 62 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.

  1. 11d ago First seen · 62 lines · 30 tokens per session scan A 4f2ce1818e40

Subscribe to this mod's changes

rig-audit is a command published in the GitHub repository Ertinox7711/SGRR-AGI-V2 (1 stars, last pushed 3d ago), licensed MIT. It adds 30 tokens to every session and 843 once invoked, about $0.0002 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.