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.
npx agentmods add skills/jmlero/claude-toolkit/audit-codenpx skills add jmlero/claude-toolkit --skill audit-codegit clone --depth 1 https://github.com/jmlero/claude-toolkitWhat 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.00042 | $0.00602 |
| Opus 5 | $0.00021 | $0.00301 |
| Sonnet 5 | $0.00008 | $0.00120 |
| Haiku 4.5 | $0.00004 | $0.00060 |
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 yesterday.
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.
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
.envfiles - SQL injection protection (parameterized queries / ORM)
- XSS protection in frontend
- Auth required on all mutating endpoints
- JWT validation on protected routes
- No
DEBUG=Trueor 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
-
.dockerignoreexcludes 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
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.
- yesterday First seen · 79 lines · 42 tokens per session scan A 205e2d53ec17
audit-code is a skill published in the GitHub repository jmlero/claude-toolkit (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 42 tokens to every session and 602 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…