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 skills add jpeslar1/john-peslar-ai-skills --skill claude-code-build-auditorgit clone --depth 1 https://github.com/jpeslar1/john-peslar-ai-skillsWrote 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/skills/jpeslar1/john-peslar-ai-skills/claude-code-build-auditor)<a href="https://agentmods.dev/skills/jpeslar1/john-peslar-ai-skills/claude-code-build-auditor"><img src="https://agentmods.dev/badge/skills/jpeslar1/john-peslar-ai-skills/claude-code-build-auditor/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/skills/jpeslar1/john-peslar-ai-skills/claude-code-build-auditor"><img src="https://agentmods.dev/badge/skills/jpeslar1/john-peslar-ai-skills/claude-code-build-auditor.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.00149 | $0.01732 |
| Opus 5 | $0.00075 | $0.00866 |
| Sonnet 5 | $0.00030 | $0.00346 |
| Haiku 4.5 | $0.00015 | $0.00173 |
Grade A, and why
claude-code-build-auditor 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 12d 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.
How it starts
The opening of the file, as written. The whole thing — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Build Auditor
Use this skill to audit an AI-assisted build like a Claude Code product engineer: delete unnecessary scaffolding, observe the model against the real codebase, add back only proven instructions, and require verification loops before trusting output.
Read references/source-map.md when the user asks where the framework came from, wants the Boris Cherny talk summarized, or wants the skill updated from a new Claude Code talk.
Core Principle
Modern coding agents often fail because the product, prompt, or workflow gets in the model's way. Do not solve every failure by adding more instructions. Start by removing bloat, run the model on the real task, observe repeated failure patterns, then add the smallest durable context, test, tool, permission, or skill that fixes the repeated failure.
When To Use This Skill
Use it at five points in a build:
- Before architecture - Decide whether the architecture is simple enough for an agent and human maintainer to reason about.
- Before a big agent run - Give the agent the task, guardrails, exit criteria, and verification path without overspecifying every step.
- During implementation drift - Stop AI bloat, duplicate abstractions, unnecessary files, speculative framework changes, and instruction sprawl.
- After a model or tool upgrade - Re-test old prompts, skills, hooks, and MCP context. Newer models may not need old scaffolding.
- Before shipping - Verify the work through tests, product behavior, logs, screenshots, readbacks, or a focused code review.
Audit Lenses
Apply these in order.
-
Delete-first ablation
- What instructions, abstractions, hooks, helper files, wrappers, or process steps can be removed?
- What happens if the agent runs with less instruction?
- Is this line here because the current model needs it, or because an older model once needed it?
-
Repeated-failure proof
- Do not add permanent instructions after one weird failure.
- Add context only when the model repeatedly stumbles on the same project-specific issue.
- Prefer a small skill, test, comment, or MCP data source over a giant prompt.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 170 lines · 149 tokens per session scan A c633604dd460
claude-code-build-auditor is a skill published in the GitHub repository jpeslar1/john-peslar-ai-skills (6 stars, last pushed 3d ago), licensed MIT. It adds 149 tokens to every session and 1,732 once invoked, about $0.0007 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
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
omh-code-review
This is a Hermes-native code-review workflow skill.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
full-repo-review
Comprehensive four-wave review of all repo source files, producing a prioritized issue backlog.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…