Borrowing it
Nothing to install: this file belongs to xsovad06/sova. 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/xsovad06/sova/main/.claude/commands/audit-instructions.mdgit clone --depth 1 https://github.com/xsovad06/sovaWrote 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/xsovad06/sova/audit-instructions)<a href="https://agentmods.dev/commands/xsovad06/sova/audit-instructions"><img src="https://agentmods.dev/badge/commands/xsovad06/sova/audit-instructions/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/xsovad06/sova/audit-instructions"><img src="https://agentmods.dev/badge/commands/xsovad06/sova/audit-instructions.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.00022 | $0.01014 |
| Opus 5.5 | $0.00009 | $0.00406 |
| Sonnet 5.5 | $0.00004 | $0.00203 |
| Haiku 4.5 | $0.00002 | $0.00101 |
Grade A, and why
audit-instructions scanned grade A with 1 finding 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 16d 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.
Enumerates other installed skillslowAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
ls .claude/skills/*/SKILL.md 2>/dev/null || echo "No skills" Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit this project's AI instruction system for completeness, contradictions, implicit assumptions, and autonomous-agent readiness. $ARGUMENTS
Phase 1: Collect All Instruction Sources
Read every instruction file. Do not skip any.
cat CLAUDE.md 2>/dev/null || echo "MISSING: CLAUDE.md"
cat AGENTS.md 2>/dev/null || echo "No AGENTS.md"
for f in .claude/rules/*.md; do [ -f "$f" ] && echo "=== $f ===" && cat "$f"; done 2>/dev/null || echo "No rules"
ls .claude/agent-memory/*.md 2>/dev/null || echo "No agent memory"
ls .claude/skills/*/SKILL.md 2>/dev/null || echo "No skills"
Phase 2: Analyze Project Reality
Understand the actual project to compare against instructions:
find . -maxdepth 3 -type f \( -name "*.py" -o -name "*.ts" -o -name "*.js" -o -name "*.go" -o -name "*.rs" -o -name "*.java" \) | head -50
git log --oneline -20 2>/dev/null || echo "Not a git repo"
ls pyproject.toml package.json Cargo.toml go.mod Makefile Dockerfile 2>/dev/null
ls -d tests/ test/ __tests__/ spec/ 2>/dev/null && find tests/ test/ __tests__/ spec/ -maxdepth 1 -name "*.py" -o -name "*.ts" -o -name "*.js" 2>/dev/null | head -20
Phase 3: Gap Analysis
For each category, assess completeness (0-10) and list specific gaps:
| Category | What to check |
|---|---|
| Build commands | Are test_cmd, lint_cmd, format_cmd documented and correct? Do they match actual tooling? |
| Architecture | Does CLAUDE.md explain the module structure? Can an agent navigate the codebase without guessing? |
| Conventions | Are naming conventions, file organization, and code style rules stated explicitly? |
| Error handling | Are error handling patterns documented? |
| Testing | Are test patterns, fixtures, mocks, and conventions documented? |
| Dependencies | Are dependency management conventions documented (add/remove/upgrade)? |
| Security | Are security-sensitive areas called out (credentials, external inputs, subprocess)? |
| Agent boundaries | Are there clear "always do" / "ask first" / "never do" boundaries? |
| Contradictions | Do any rules conflict with each other or with actual project practice? |
| Implicit assumptions | What does the project assume that is not written down? |
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.
- 16d ago Changed 4eb0023dcd1d
- 2mo ago First seen · 120 lines · 22 tokens per session scan A 21269b1b5592
audit-instructions is a command published in the GitHub repository xsovad06/sova (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 22 tokens to every session and 1,014 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (enumerates other installed skills). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
greptile-review
Execute the full Greptile review cycle on a PR, looping until score meets threshold or circuit breaker triggers.
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.
review
Review current changes for correctness, style, and potential issues.
advanced-code-review-context
Advanced Code Review Phase 2: Context Analysis - load previous reviews, PR history, declined items.
code-review-give
Give mode for code-review: Review someone else's code with multi-pass analysis and structured recommendations.
mach12:issue-review
Read a GitHub issue and all comments, review the implementation plan, and present findings.