audit-plan

audit-plan is a skill for Claude Code from MinhThang1009/dotclaude. It costs 173 tokens per session (4,639 once invoked), scanned A, original, MIT.

A tool for checking a written implementation plan against the actual codebase, the project's source files and configuration. It can find missing work, run planned cleanup checks, and inspect whether test cases cover each phase.

In plain words
What is it for?
Use it to audit migration, refactoring, and feature plans; list documented gaps; verify dead-code cleanup commands; and check planned test coverage.
Why use it?
It catches gaps, untested phases, and leftover code before implementation begins, when they are cheaper to fix.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths.

Part of the audit-plan plugin — 1 skill shipped together

Good fit Use it to audit migration, refactoring, and feature plans; list documented gaps; verify dead-code cleanup commands; and check planned test coverage.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/minhthang1009/dotclaude/audit-plan
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 MinhThang1009/dotclaude --skill audit-plan
Clone the repo
git clone --depth 1 https://github.com/MinhThang1009/dotclaude

Made for: Claude Code.

Or install audit-plan, 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.

agentmods badge for audit-plan

README.md
[![agentmods](https://agentmods.dev/badge/skills/minhthang1009/dotclaude/audit-plan/github.svg)](https://agentmods.dev/skills/minhthang1009/dotclaude/audit-plan)
Your own site
<a href="https://agentmods.dev/skills/minhthang1009/dotclaude/audit-plan"><img src="https://agentmods.dev/badge/skills/minhthang1009/dotclaude/audit-plan/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.

agentmods 80×15 button for audit-plan

Your own site · 80×15
<a href="https://agentmods.dev/skills/minhthang1009/dotclaude/audit-plan"><img src="https://agentmods.dev/badge/skills/minhthang1009/dotclaude/audit-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 173 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,639 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00173 $0.04639
Opus 5 $0.00086 $0.02320
Sonnet 5 $0.00035 $0.00928
Haiku 4.5 $0.00017 $0.00464

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

Security

Grade A, and why

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

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-plan/skills/audit-plan/SKILL.md · 217 lines

How it starts

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

Skill: Audit Plan

Audit a plan file (migration, refactor, feature, etc.) against the actual codebase.

Sub-commands

Parse $ARGUMENTS to determine which mode to run. Match sub-command tokens case-insensitively (Gaps = gaps):

First token Mode What it does
(empty or path) Full audit Loop scan until 0 new gaps. Default mode.
gaps List gaps Read plan, list all ### Gap entries as a numbered table. No scanning.
verify Run cleanup checklist Execute every grep command in the plan's Dead Code Removal Checklist. Report pass (0 matches) or fail (N matches) per command.
tests Check test coverage For each phase, count - [ ] test cases. Flag phases with 0 tests. Flag gaps that have no corresponding test case.

If the remaining token after the sub-command is a file path, use it as the plan file. If that explicit path does not exist or cannot be read → STOP and report: audit-plan: '<path>' not found. — do NOT silently fall back to auto-detect. Any tokens beyond [subcommand] [path] → report audit-plan: unrecognized arguments: <tokens> and stop. Otherwise, auto-detect:

  1. Project-level: .claude/plans/*.md in the current working directory. Use this — if multiple files exist, pick the most recently modified one. An auto-detected file that exists but cannot be read → same STOP-and-report as an explicit path (do not silently skip to another file).
  2. No project-level plans found: Do NOT fallback to global ~/.claude/plans/ — those may belong to other projects. Instead, report error: "No plan files found in .claude/plans/. Specify a path: /audit-plan:audit-plan <path>"

Step 0: Input-format guard (run BEFORE any mode)

audit-plan expects a gap-tracking plan: ### Gap N: entries, a Dead Code Removal / Cleanup Checklist with grep commands, and - [ ] test checklists. Before running any mode, grep the plan for these three markers:

  • ### Gap
  • - [ ]
  • grep commands inside a cleanup/checklist section — a section whose heading contains "cleanup", "checklist", or "removal" (case-insensitive) and does NOT contain "test"; a line counts even when wrapped in a list marker (- [ ], -, *, numbering)

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

  1. 9d ago First seen · 217 lines · 173 tokens per session scan A d14f748c31f2

Subscribe to this mod's changes

audit-plan is a skill published in the GitHub repository MinhThang1009/dotclaude (20 stars, last pushed 1mo ago), licensed MIT. It adds 173 tokens to every session and 4,639 once invoked, about $0.0009 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-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens