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.
git clone --depth 1 https://github.com/pluginslab/wp-agentic-kitWrote 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/commands/pluginslab/wp-agentic-kit/audit-plan)<a href="https://agentmods.dev/commands/pluginslab/wp-agentic-kit/audit-plan"><img src="https://agentmods.dev/badge/commands/pluginslab/wp-agentic-kit/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.
<a href="https://agentmods.dev/commands/pluginslab/wp-agentic-kit/audit-plan"><img src="https://agentmods.dev/badge/commands/pluginslab/wp-agentic-kit/audit-plan.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.00030 | $0.00320 |
| Opus 5.5 | $0.00012 | $0.00128 |
| Sonnet 5.5 | $0.00006 | $0.00064 |
| Haiku 4.5 | $0.00003 | $0.00032 |
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 1mo 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.
What it actually says
Audit plan
Dispatch the plan-reviewer sub-agent to audit a feature plan before human review.
- If
$ARGUMENTSis empty, locate the active feature: the most recently modified.claude/plans/features/*/progress.mdwhosestatus:is notcomplete|done|shipped|archived|completed. Use its directory's basename as the slug. - If
$ARGUMENTSis non-empty, use it as the slug. Verify.claude/plans/features/$ARGUMENTS/exists. - Invoke the
plan-reviewersub-agent with this instruction:Audit
.claude/plans/features/<slug>/. Check spec.md, plan.md, findings.md (if present), and constitution.md per the rules in.claude/agents/plan-reviewer.md. Report findings grouped by severity. - Surface the report back to me grouped by severity (Critical / High / Medium / Low).
- If Critical findings exist: tell me which ones and stop — they need fixing before the plan PR can be merged.
- If only Medium/Low findings exist: list them and ask whether to fix now or merge anyway.
- If clean: confirm the plan is ready for human review and (if a plan PR isn't open yet) offer to run
/plan-freeze.
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.
- 1mo ago First seen · 18 lines · 30 tokens per session scan A 78870a67a014
audit-plan is a command published in the GitHub repository pluginslab/wp-agentic-kit (20 stars, last pushed 1mo ago), licensed MIT. It adds 30 tokens to every session and 320 once invoked, about $0.0001 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-30.
Other commands, from other repositories
audit-agents-skills
Audit quality of agents, skills, and commands in a Claude Code project.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
review
Review the current diff against project memory.
advanced-code-review-context
Advanced Code Review Phase 2: Context Analysis - load previous reviews, PR history, declined items.
code-review-give
Give mode for code-review: Review someone else's code with multi-pass analysis and structured recommendations.
review-design-verify
Phases 4-5 of reviewing-design-docs: Interface Verification + Implementation Simulation.