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/xbim08/awesome-claude-code-plugins/auditgit clone --depth 1 https://github.com/xbim08/awesome-claude-code-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.00006 | $0.00201 |
| Opus 5 | $0.00003 | $0.00101 |
| Sonnet 5 | $0.00001 | $0.00040 |
| Haiku 4.5 | $0.00001 | $0.00020 |
Grade A, and why
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 yesterday.
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 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.
What it actually says
Context
- Package.json dependencies: @package.json
- Environment files: !
find . -name ".env*" -o -name "config.*" | head -10 - Potential security files: !
find . -name "*secret*" -o -name "*key*" -o -name "*password*" | head -10
Your task
Perform a security audit focusing on:
- Dependency vulnerabilities: Check for known CVEs
- Authentication/Authorization: Review auth implementations
- Input validation: Check for injection vulnerabilities
- Data exposure: Look for sensitive data leaks
- Configuration security: Review security configurations
- Secrets management: Ensure proper secret handling
Target: $ARGUMENTS (if specified, otherwise audit entire codebase)
Provide prioritized findings with remediation steps.
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.
- yesterday First seen · 25 lines · 6 tokens per session scan A ad478b66fce0
audit is a command published in the GitHub repository xbim08/awesome-claude-code-plugins (10 stars, last pushed yesterday), licensed Apache-2.0. It adds 6 tokens to every session and 201 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to audit, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
workflow-from-spec
Design a complete multi-agent workflow from a natural language description, selecting the right orchestration pattern.
create-hook
Create hooks with brainstorming and security-first design.
evaluate-skill
Manually evaluate a recent skill execution to record qualitative feedback.
team-standup
Generate a team standup summary using the shared team log and individual context.
atl-fetch-jira
Command "atl-fetch-jira" from lc-semba-ryuichiro/semba-claude-plugins, covering jira 情報取得コマンド, コマンド実行, オプション, 実行例 and 課題情報を取得（json）.
pr-desc
Reads git diff between the current branch and main (or a specified base branch), analyzes changed files, and generates a structured pull request description ready to paste into GitHub.