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 faizkhairi/claude-code-blueprint --skill self-auditgit clone --depth 1 https://github.com/faizkhairi/claude-code-blueprintWrote 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/faizkhairi/claude-code-blueprint/self-audit)<a href="https://agentmods.dev/skills/faizkhairi/claude-code-blueprint/self-audit"><img src="https://agentmods.dev/badge/skills/faizkhairi/claude-code-blueprint/self-audit.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Agent Snooping · line 28 Skill reads from agent configuration directories (.claude/, .codex/, .gemini/). These directories may contain API keys, personal settings, and other credentials that the skill has no legitimate need to access.Fix: Remove all code or instructions that access agent configuration directories (.claude/, .codex/, .gemini/). If configuration values are needed, pass them explicitly as parameters or environment variabl
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.00090 | $0.00790 |
| Opus 5 | $0.00045 | $0.00395 |
| Sonnet 5 | $0.00018 | $0.00158 |
| Haiku 4.5 | $0.00009 | $0.00079 |
Grade A, and why
self-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 9d 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.
Reads agent configuration directorieslowAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
grep -rn "<resource>" ~/.claude/skills ~/.claude/agents ~/.claude/hooks ~/.claude/rules Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Self-audit YOUR OWN plan before ExitPlanMode. This is an attention-gap backstop: the verify-plan checklist already exists in this blueprint (the verify-plan agent), but knowing a check and applying it at the right moment are different things. This skill forces the full checklist to run against the plan you just wrote, catching blind spots you missed while heads-down in planning.
When this runs
- Automatically: before every non-trivial
ExitPlanMode(per the Plan-First rule in CLAUDE.md). A plan is non-trivial if it touches more than one file, changes behavior, or modifies config or a shared resource. - On demand: when the user says "audit yourself", "did you check everything", and similar.
Skip only for genuinely trivial plans (a single-line typo fix).
What it does
- Read the current plan: the plan file named in the plan-mode system message.
- Run the verify-plan checklist against the plan, IN ORDER. Do not re-derive it: spawn the
verify-planagent (or readagents/verify-plan.mdand follow its checklist) so the same checks that would review someone else's plan now review yours. Report a table: Check | Status (PASS / FAIL / UNCLEAR) | Finding. - Emphasis on the Consumer Audit, the highest-value and most-missed check:
- Identify every SHARED RESOURCE the plan changes: a token or credential, an env key, a file path, a DB table, an API field, or any string referenced from more than one place.
- For each, grep BOTH the target repo AND your own global config, because a repo-only search misses consumers that live in your personal setup:
# Repo: grep -rn "<resource>" . # Your own global config (adjust to your layout): grep -rn "<resource>" ~/.claude/skills ~/.claude/agents ~/.claude/hooks ~/.claude/rules - Every hit is a consumer. Ask: "does the plan repoint or update this, or will it break silently?" If a consumer is not handled in the plan, that is a FAIL: add it to the plan before exiting.
- This is the exact class of miss where a plan updates a shared value in the repo but leaves stale references in the user's own global config (a repo-only audit reports "zero consumers" while several live outside the repo).
- On any FAIL: fix the plan file first, then re-run the failed checks. Only proceed to ExitPlanMode when the audit is clean, or the remaining items are explicitly accepted or deferred with a reason.
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.
- 9d ago First seen · 43 lines · 90 tokens per session scan A f6c1e7b1791d
self-audit is a skill published in the GitHub repository faizkhairi/claude-code-blueprint (70 stars, last pushed 27d ago), licensed MIT. It adds 90 tokens to every session and 790 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
nft-standards
Implement NFT standards (ERC-721, ERC-1155) with proper metadata handling, minting strategies, and marketplace integration. Use when creating NFT contracts, building NFT marketplaces, or implementing digital asset systems.
postgresql-table-design
Use this skill when designing or reviewing a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features.
istio-traffic-management
Configure Istio traffic management including routing, load balancing, circuit breakers, and canary deployments. Use when implementing service mesh traffic policies, progressive delivery, or resilience patterns.
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
workflow-orchestration-patterns
Design durable workflows with Temporal for distributed systems. Covers workflow vs activity separation, saga patterns, state management, and determinism constraints. Use when building long-running processes, distributed transactions, or microservice orchestration.
microservices-patterns
Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing microservices.