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.
git clone --depth 1 https://github.com/ArogyaReddy/alirezarezvani-claude-skillsnpx agentmods add commands/arogyareddy/alirezarezvani-claude-skills/plugin-auditWrote 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/arogyareddy/alirezarezvani-claude-skills/plugin-audit)<a href="https://agentmods.dev/commands/arogyareddy/alirezarezvani-claude-skills/plugin-audit"><img src="https://agentmods.dev/badge/commands/arogyareddy/alirezarezvani-claude-skills/plugin-audit.svg" alt="Measured on agentmods" 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.00014 | $0.01539 |
| Opus 5 | $0.00007 | $0.00770 |
| Sonnet 5 | $0.00003 | $0.00308 |
| Haiku 4.5 | $0.00001 | $0.00154 |
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 7d 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.
This is a copy
100% identical to plugin-audit — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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
$ARGUMENTSexists and containsSKILL.md. If not, error and stop. - Read
SKILL.mdfrontmatter — extractname,description,Category,Tier. - Detect components:
scripts/*.py→ Python tools (count them)references/*.md→ reference docs (count them)assets/→ templates/samplesexpected_outputs/→ test fixturesagents/*.md→ embedded agentsskills/*/SKILL.md→ sub-skills (compound skill).claude-plugin/plugin.json→ standalone pluginsettings.json→ command registrations
- Detect domain from path (
engineering/,product-team/,marketing-skill/, etc.) - Search
commands/for a.mdfile 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
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.
- 7d ago First seen · 154 lines · 14 tokens per session scan A cd656f6c9fe7
plugin-audit is a command published in the GitHub repository ArogyaReddy/alirezarezvani-claude-skills (31 stars, last pushed 5mo ago), licensed MIT. It adds 14 tokens to every session and 1,539 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to plugin-audit, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.