A batch checker for production code that scores files against defined quality checks and catalogs of unwanted coding patterns. It can audit a whole project, a directory, or an individual file.

Use it for release preparation, codebase health checks, or reviewing many production files after major changes. It can also limit checks to service files.

It gives a consistent, evidence-based view of code quality and highlights critical failures and priority fixes. Quick mode provides pass/fail results, while deep mode gathers more evidence.

code-audit — Skill by greglas75

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 skills/greglas75/zuvo/code-audit

Any agent

npx skills add greglas75/zuvo --skill code-audit

Clone the repo

git clone --depth 1 https://github.com/greglas75/zuvo

Made for: Claude Code, Codex.

Per session 83 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

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

Security scan A 1 finding. 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.

Model	Per session	Once invoked
Fable 5	$0.00083	$0.11802
Opus 5	$0.00042	$0.05901
Sonnet 5	$0.00017	$0.02360
Haiku 4.5	$0.00008	$0.01180

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

Security

Grade A, and why

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

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

CAP26: `subprocess`/`os.system` with `shell=True` or a non-literal command string (CWE-78) -- AUTO TIER-D [stack: python]

skills/code-audit/SKILL.md · 787 lines

How it starts

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

zuvo:code-audit — Production Code Quality Triage

Systematic evaluation of production source files through the CQ1-CQ40 binary checklist and CAP anti-pattern catalog. Every file receives a tier classification based on its score, critical gate status, and detected anti-patterns. The output is a prioritized report with actionable fix plans.

When to use: Periodic health checks, before major releases, after adding many production files, when onboarding a new codebase, when code quality feels inconsistent. Out of scope: Single-file code review (use zuvo:review), refactoring (use zuvo:refactor), test quality assessment (use zuvo:test-audit), feature development (use zuvo:build).

Argument Parsing

Argument	Effect
`all`	Audit every production file in the project
`[path]`	Audit production files under a specific directory
`[file]`	Audit a single file with full evidence (forces deep mode)
`--deep`	Collect per-gate evidence and fix recommendations for every file
`--quick`	Binary pass/fail only, skip evidence gathering
`--services` (filter Phase 0.1 discovery to files classified SERVICE in 0.3; without that filter this flag is a no-op)	Restrict scope to service and business logic files
`--controllers` (same: filter Phase 0.1 to CONTROLLER-classified files)	Restrict scope to controller, handler, and route files

Default behavior: all --quick

Mode	Scope	Depth	Batch Size	Notes
`all`	Entire project	Standard	6 files/batch	Default
`[path]`	Directory tree	Standard	6 files/batch	Scoped
`[file]`	One file	Deep (full evidence)	1	Single-file deep dive
`--deep`	Any scope	Full evidence	6 files/batch	Slower, thorough
`--quick`	Any scope	Binary only	10 files/batch	Fast triage
`--services`	Service files	Standard	6	Filter by file type
`--controllers`	Controller files	Standard	6	Filter by file type

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

2d ago First seen · 787 lines · 83 tokens per session scan A 9ce1a89f20fa

Subscribe to this mod's changes

code-audit is a skill published in the GitHub repository greglas75/zuvo (6 stars, last pushed 2d ago), licensed MIT. It adds 83 tokens to every session and 11,802 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Code review Code/Test audits Git and workflow Testing ai-coding claude-code claude-code-plugin code-quality codex

ring:applying-composition-patterns

React composition patterns that scale. Avoid boolean prop proliferation by using compound components, lifting state, and composing internals. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or during architecture review. Skip for simple components with 1-2 props…

LerianStudio/ring · 68 tokens

ring:adopting-lib-commons-huma-wrapper

Adopting the lib-commons/v5 shared Huma (OAS 3.1) OpenAPI wrapper + RFC 9457 problem model (commons/net/http/{openapi,problem}) in a Lerian Go service: wire openapi.New/ServeSpec + problem.Install (central >=500 scrub) on BOTH runtime and spec-gen paths, the per-rail problem.MapError flex seam, and rename-only spec…

LerianStudio/ring · 142 tokens

ring:searching-code

Forensic code search and analysis with optional Chain of Draft (CoD) ultra-concise mode. Five-phase methodology (clarification, planning, execution, analysis, synthesis) with severity assessment. Use for targeted investigation of specific patterns, bugs, or vulnerabilities. Skip for broad architecture mapping (use…

LerianStudio/ring · 74 tokens

ring:exploring-codebases

Exploring a codebase across phases: scopes the target, detects architecture, components, and layers, deep-dives each discovered perspective, then synthesizes findings into actionable guidance with file:line evidence. Use to understand how a feature or system works before planning changes, or to orient on an unfamiliar…

LerianStudio/ring · 91 tokens

ring:opening-pull-requests

Open a GitHub Pull Request with automatic base branch detection, scope allowlist enforcement, PR template filling, and post-create base verification. Replaces ring:generating-pr-descriptions. Use after pushing a branch when ready to open a PR. Skip if the branch is not yet pushed or there are uncommitted changes …

LerianStudio/ring · 83 tokens

ring:fixing-lint

Fixing lint to a clean state: runs the linter, groups reported issues into independent streams, and dispatches one parallel fixer agent per stream (ring:backend-go for Go, ring:general-purpose otherwise), iterating until clean. Use when a codebase has lint errors across multiple files. Skip for a single error (fix…

LerianStudio/ring · 96 tokens

code-audit