audit-codebase

A command for scanning a codebase and producing a Markdown report about its structural health. It looks at folders, file sizes, nesting, naming, unused files, empty directories, and documentation sprawl.

In plain words
What is it for?
Use it to audit a repository, identify organisation and maintenance issues, and create either a comprehensive report or a shorter implementation specification.
Why use it?
Structural problems are easy to overlook when working on individual files. A report makes those problems visible and groups possible cleanup into implementation phases.

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/drakaniia/skills/audit-codebase
Clone the repo
git clone --depth 1 https://github.com/Drakaniia/skills
Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 126 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.00016 $0.00126
Opus 5 $0.00008 $0.00063
Sonnet 5 $0.00003 $0.00025
Haiku 4.5 $0.00002 $0.00013

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

Security

Grade A, and why

audit-codebase 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.

commands/audit-codebase.md · 9 lines

What it actually says

Run the audit-codebase skill to scan this codebase for structural health issues. Generate a full markdown audit report with before/after diagrams organized by refactoring phases.

Use the ask_user tool to ask the user if they want a full report (comprehensive) or quick spec (fast-track for AI implementation). Then scan the codebase, detect issues (folder bloat, oversized files, deep nesting, naming inconsistencies, orphaned files, doc sprawl, empty directories), and save the report.

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 · 9 lines · 16 tokens per session scan A 896c4207a3aa

Subscribe to this mod's changes

audit-codebase is a command published in the GitHub repository Drakaniia/skills (7 stars, last pushed 12d ago), licensed Apache-2.0. It adds 16 tokens to every session and 126 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-08-31.