What is plugin-audit?

A full audit process for checking a skill directory. A skill directory is a folder of instructions and supporting files that an AI coding assistant can use.

Use it to inspect a skill's files, validate its structure, detect related commands and components, run checks, and automatically fix non-critical problems.

It finds missing files, structural problems, weak documentation, security issues, and other quality concerns before a skill is shared or released.

plugin-audit — Command for Claude Code by alirezarezvani/claude-skills

About the project

claude-skills is a large collection of reusable skills, commands, plugins, and supporting resources for coding agents across engineering, business, research, compliance, and productivity work. It is used by people who want agents such as Claude Code, Codex, Gemini CLI, or Cursor to follow specialized workflows. The catalogue contains selected skills and settings from the collection.

alirezarezvani/claude-skills · 28,240 stars · on GitHub · alirezarezvani.medium.com

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

git clone --depth 1 https://github.com/alirezarezvani/claude-skills

agentmods

npx agentmods add commands/alirezarezvani/claude-skills/plugin-audit

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/alirezarezvani/claude-skills/plugin-audit/github.svg)](https://agentmods.dev/commands/alirezarezvani/claude-skills/plugin-audit)

Your own site

<a href="https://agentmods.dev/commands/alirezarezvani/claude-skills/plugin-audit"><img src="https://agentmods.dev/badge/commands/alirezarezvani/claude-skills/plugin-audit/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/alirezarezvani/claude-skills/plugin-audit"><img src="https://agentmods.dev/badge/commands/alirezarezvani/claude-skills/plugin-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,539 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.

Model	Per session	Once invoked
Fable 5.1	$0.00014	$0.01539
Opus 5.5	$0.00006	$0.00616
Sonnet 5.5	$0.00003	$0.00308
Haiku 4.5	$0.00001	$0.00154

Measured 1mo ago against content hash cd656f6c9fe7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

Origin

Copies of this mod

2 near-identical copies found in the catalogue:

plugin-audit — 100% identical, 0 lines differ
plugin-audit — 100% identical, 0 lines differ

.claude/commands/plugin-audit.md · 154 lines

How it starts

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

Run the comprehensive plugin audit pipeline on the skill at $ARGUMENTS. If no argument provided, ask the user for the skill path.

Execute all 8 phases sequentially. Auto-fix non-critical issues. Only prompt the user for critical decisions (external dependencies, security findings, breaking changes).

Phase 1: Discovery

Verify $ARGUMENTS exists and contains SKILL.md. If not, error and stop.
Read SKILL.md frontmatter — extract name, description, Category, Tier.
Detect components:
- scripts/*.py → Python tools (count them)
- references/*.md → reference docs (count them)
- assets/ → templates/samples
- expected_outputs/ → test fixtures
- agents/*.md → embedded agents
- skills/*/SKILL.md → sub-skills (compound skill)
- .claude-plugin/plugin.json → standalone plugin
- settings.json → command registrations
Detect domain from path (engineering/, product-team/, marketing-skill/, etc.)
Search commands/ for a .md file matching the skill name.
Display discovery summary.

Phase 2: Structure Validation

Run:

python3 engineering/skill-tester/scripts/skill_validator.py $ARGUMENTS --json

Parse JSON. If score < 75:

Auto-fix missing frontmatter fields, missing section headings, missing directories.
Re-run. If still < 75, mark as FAIL but continue collecting results.

Phase 3: Quality Scoring

Run:

python3 engineering/skill-tester/scripts/quality_scorer.py $ARGUMENTS --detailed --json

Parse JSON. If score < 60, report improvement roadmap items.

Phase 4: Script Testing

If $ARGUMENTS/scripts/ contains .py files, run:

python3 engineering/skill-tester/scripts/script_tester.py $ARGUMENTS --json --verbose

All scripts must PASS. If any script uses external imports, ask the user whether the dependency is acceptable.

Phase 5: Security Audit

Run:

python3 engineering/skill-security-auditor/scripts/skill_security_auditor.py $ARGUMENTS --strict --json

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

1mo ago First seen · 154 lines · 14 tokens per session scan A cd656f6c9fe7

Subscribe to this mod's changes

plugin-audit is a command published in the GitHub repository alirezarezvani/claude-skills (28,240 stars, last pushed 1mo ago), licensed MIT. It adds 14 tokens to every session and 1,539 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.

Code review agent-plugins agent-skills agentic-ai ai-coding-agent anthropic-claude claude-ai

plugin-audit

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

Copies of this mod

How it starts

Phase 1: Discovery

Phase 2: Structure Validation

Phase 3: Quality Scoring

Phase 4: Script Testing

Phase 5: Security Audit

What this file has done since we first saw it

Other commands, from other repositories

validate-pr-description

analyst

review-feedback

address

translate-review-to-single-human

qa-loop