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 agentmods add commands/sgaunet/claude-plugins/audit-pluginsgit clone --depth 1 https://github.com/sgaunet/claude-pluginsWhat 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 | $0.00011 | $0.01878 |
| Opus 5 | $0.00005 | $0.00939 |
| Sonnet 5 | $0.00002 | $0.00376 |
| Haiku 4.5 | $0.00001 | $0.00188 |
Grade A, and why
audit-plugins 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit Plugins Command
Scan all plugin definitions in this marketplace and compare them against official Claude Code documentation. Produce a scored audit report with prioritized findings.
Process
Step 1: Discover Plugin Structure
Use Glob to enumerate all files to audit:
plugins/*/agents/*.md— agent definitionsplugins/*/commands/*.md— command definitionsplugins/*/skills/*/SKILL.md— skill definitionsplugins/*/.claude-plugin/plugin.json— plugin manifests.claude-plugin/marketplace.json— marketplace manifestplugins/*/.mcp.json— MCP server configurations
Count totals (plugins, agents, commands, skills) for the report summary.
Step 2: Launch 3 Parallel Sonnet Agents
Launch all 3 agents concurrently using the Task tool. Each agent must first fetch the relevant official documentation via WebFetch before performing its analysis.
Agent 1: Agent & Subagent Auditor (general-purpose, model: sonnet)
Prompt the agent to:
- Fetch official docs using WebFetch:
https://docs.claude.com/en/docs/claude-code/plugins-reference— extract agent frontmatter fields, required vs optional, content structurehttps://docs.claude.com/en/docs/claude-code/sub-agents— extract sub-agent best practices, model selection guidance
- Read all files matching
plugins/*/agents/*.md - For each agent file, check:
- Frontmatter fields:
name(required),description(required),model(required, valid values: sonnet/opus/haiku),allowed-tools(recommended),color(optional),context(optional),permissionMode(optional),capabilities(optional),skills(optional) - Description quality: Should clearly state WHEN to use the agent (shown in Claude Code UI)
- Model appropriateness:
sonnetfor code/speed tasks,opusfor complex analysis/docs,haikufor fast/simple tasks - Content structure: Should include role statement, proactive triggers, core capabilities, implementation patterns, deliverables
- Proactive triggers: File patterns and keyword triggers for automatic activation
- Tool restrictions:
allowed-toolsshould be scoped appropriately (not overly broad)
- Frontmatter fields:
- Return findings with severity levels and file references
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.
- 2d ago First seen · 166 lines · 11 tokens per session scan A 631c6f451408
audit-plugins is a command published in the GitHub repository sgaunet/claude-plugins (16 stars, last pushed 7d ago), licensed MIT. It adds 11 tokens to every session and 1,878 once invoked, about $0.0001 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.
Other commands, from other repositories
security-audit-static
Static security audit of AI-built code — map trust boundaries, cross-reference documented intent, self-refute every finding, and report only evidence-backed risks.
performance-audit-static
Static performance audit of AI-built code — find N+1 queries and request waterfalls, over-fetching, missing indexes, and caching opportunities, ranked by effort and impact.
sprint
Sprint lifecycle — plan a sprint, run a retrospective, or generate release notes.
document-app
Reverse-engineer an AI-built codebase into the system documents reviewers and auditors need — a core set (architecture, flows, permissions, variables) plus conditional docs (emails, cron, SEO, automation) when they apply.
analyze-test
Analyze A/B test results — statistical significance, sample size validation, and ship/extend/stop recommendations.
plan-okrs
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results.