A checklist for judging whether a codebase is ready to run in production, the live environment used by real users. It checks security, errors, login controls, input handling, database use, Docker, and coding standards.

Use it before deployment or during a broad code-quality review to inspect security settings, API behavior, validation, database access, and infrastructure configuration.

It helps find deployment risks and quality problems before users encounter them. Findings are marked as pass, warning, or failure.

audit-code — Skill for Claude Code by jmlero/claude-toolkit

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.

Any agent

npx skills add jmlero/claude-toolkit --skill audit-code

Clone the repo

git clone --depth 1 https://github.com/jmlero/claude-toolkit

Made for: Claude Code.

Or install audit-code, the plugin that ships this one along with the rest of its 1 skill.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/jmlero/claude-toolkit/audit-code/github.svg)](https://agentmods.dev/skills/jmlero/claude-toolkit/audit-code)

Your own site

<a href="https://agentmods.dev/skills/jmlero/claude-toolkit/audit-code"><img src="https://agentmods.dev/badge/skills/jmlero/claude-toolkit/audit-code/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/jmlero/claude-toolkit/audit-code"><img src="https://agentmods.dev/badge/skills/jmlero/claude-toolkit/audit-code.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 602 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.

Model	Per session	Once invoked
Fable 5.1	$0.00042	$0.00602
Opus 5.5	$0.00017	$0.00241
Sonnet 5.5	$0.00008	$0.00120
Haiku 4.5	$0.00004	$0.00060

Measured 2mo ago against content hash 205e2d53ec17, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

audit-code 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 2mo 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/audit-code/skills/audit-code/SKILL.md · 79 lines

How it starts

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

Perform a comprehensive production readiness audit of this codebase.

Audit Categories

Check each category and report findings as: PASS, WARN, or FAIL.

1. Security

CORS restricted to known frontend URL (not * with credentials)
No secrets in code or committed .env files
SQL injection protection (parameterized queries / ORM)
XSS protection in frontend
Auth required on all mutating endpoints
JWT validation on protected routes
No DEBUG=True or verbose errors exposed to clients

2. Error Handling

Generic error messages to clients (no stack traces leaked)
Full error details logged server-side only
Proper HTTP status codes (400 vs 500 vs 401 vs 403)
Frontend handles error/loading/empty states

3. Input Validation

Request/input models validate all API inputs (Pydantic, Zod, JSON Schema, etc.)
File upload validation (type, size)
Path parameters validated (UUID format, numeric IDs)
Query parameters have sensible defaults and limits

4. Database

No unbounded queries (pagination on list endpoints)
Proper indexes on frequently queried columns
Foreign keys with appropriate cascade behavior
Connection pooling configured

5. Docker & Infrastructure

Containers run as non-root user
No unnecessary ports exposed
Health checks defined
Production Dockerfiles use multi-stage builds
.dockerignore excludes unnecessary files

6. Code Quality

No TODO/FIXME/HACK without linked issue
No commented-out code blocks
Consistent code patterns across modules
Tests exist for critical paths

7. Dependencies

No known critical vulnerabilities
Dependency versions pinned
Unused dependencies removed

Output Format

# Production Readiness Audit

## Summary
- PASS: X | WARN: Y | FAIL: Z

## Critical Findings (FAIL)
1. [Category] Description - File:Line - Recommendation

## Warnings (WARN)
1. [Category] Description - File:Line - Recommendation

## Passed Checks
- [Category] Description

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

2mo ago First seen · 79 lines · 42 tokens per session scan A 205e2d53ec17

Subscribe to this mod's changes

audit-code is a skill published in the GitHub repository jmlero/claude-toolkit (2 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 42 tokens to every session and 602 once invoked, about $0.0002 per session on Opus 5.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.

Code review Security

audit-code next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
audit-codejmlero/claude-toolkit	Skill	2	6mo ago	Apache-2.0	A	42	Claude Code
autoreviewopenclaw/clawhub	Skill	9.5k	today	MIT	A	17	Claude Code, Codex
agent-teams-simplify-and-hardenLeoYeAI/openclaw-master-skills	Skill	2.2k	6d ago	MIT	A	115	Claude Code, Codex
omh-code-reviewrlaope/oh-my-hermes	Skill	5.2k	today	MIT	A	48	Claude Code, Codex
revdiff-planumputun/revdiff	Skill	947	2d ago	MIT	A	84	Claude Code
explore-unknownsdzhng/skills	Skill	1.4k	today	MIT	A	162	Claude Code, Codex
re0-mergeLilMGenius/paperthin	Skill	1.4k	4d ago	MIT	A	70	Claude Code