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/claude-code-community-ireland/claude-code-resources/auditgit clone --depth 1 https://github.com/Claude-Code-Community-Ireland/claude-code-resourcesWrote 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/claude-code-community-ireland/claude-code-resources/audit)<a href="https://agentmods.dev/commands/claude-code-community-ireland/claude-code-resources/audit"><img src="https://agentmods.dev/badge/commands/claude-code-community-ireland/claude-code-resources/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 | $0.00014 | $0.00460 |
| Opus 5 | $0.00007 | $0.00230 |
| Sonnet 5 | $0.00003 | $0.00092 |
| Haiku 4.5 | $0.00001 | $0.00046 |
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 4d 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 Workflow
You are running a comprehensive audit of the codebase.
Steps
-
Determine scope: Read
$ARGUMENTSto select audit type:security— OWASP vulnerabilities, auth, injection, secretsdeps— Dependency vulnerabilities, outdated packages, license complianceperf— Performance bottlenecks, N+1 queries, bundle sizeall(default) — Run all audit types
-
Run audits based on scope:
Security audit — Use the Task tool to spawn the
security-auditoragent:Run a full security audit of this codebase. Check OWASP Top 10, authentication, authorization, input validation, secrets exposure, and dependency vulnerabilities. Provide severity-rated findings with remediation steps.
Dependency audit — Run available package audit tools:
- Detect package manager (npm, yarn, pip, cargo, go)
- Run the appropriate audit command (
npm audit,pip-audit,cargo audit, etc.) - Check for outdated packages
- Scan licenses for compliance
Performance audit — Analyze code for common performance issues:
- Look for N+1 query patterns
- Check for missing database indexes on queried fields
- Identify unbounded data fetching (no pagination/limits)
- Check for memory leak patterns (uncleaned listeners, subscriptions)
- Analyze bundle size if applicable
-
Synthesize findings: Merge all results into a single prioritized report:
## Audit Report ### Critical (fix immediately) ... ### High (fix this sprint) ... ### Medium (plan to address) ... ### Low (consider improving) ... ### Summary X critical, Y high, Z medium, W low findings. -
Suggest next steps: Recommend the top 3 actions to take based on findings.
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.
- 4d ago First seen · 56 lines · 14 tokens per session scan A 7ea95213b6f1
audit is a command published in the GitHub repository Claude-Code-Community-Ireland/claude-code-resources (10 stars, last pushed 3mo ago), licensed MIT. It adds 14 tokens to every session and 460 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-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.