audit

audit is a command for coding agents from Claude-Code-Community-Ireland/claude-code-resources. It costs 14 tokens per session (460 once invoked), scanned A, original, MIT.

A command for checking a codebase for security problems, dependency issues, performance bottlenecks, and code-quality concerns.

In plain words
What is it for?
Use it for security checks, package and licence reviews, performance checks such as slow database access or oversized bundles, or all of these together.
Why use it?
It brings several types of technical review into one audit and reports findings with severity and suggested fixes.

Command

Part of the vibeworks-library plugin — 1 skill, 21 commands, 34 agents, 3 hooks shipped together

Install

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.

agentmods
npx agentmods add commands/claude-code-community-ireland/claude-code-resources/audit
Clone the repo
git clone --depth 1 https://github.com/Claude-Code-Community-Ireland/claude-code-resources

Or install vibeworks-library, the plugin that ships this one along with the rest of its 1 skill, 21 commands, 34 agents, 3 hooks.

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.

agentmods badge for audit

README.md
[![agentmods](https://agentmods.dev/badge/commands/claude-code-community-ireland/claude-code-resources/audit.svg)](https://agentmods.dev/commands/claude-code-community-ireland/claude-code-resources/audit)
Your own site
<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>
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 460 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce 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

Measured 4d ago against content hash 7ea95213b6f1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

plugins/vibeworks-library/commands/audit.md · 56 lines

What it actually says

Audit Workflow

You are running a comprehensive audit of the codebase.

Steps

  1. Determine scope: Read $ARGUMENTS to select audit type:

    • security — OWASP vulnerabilities, auth, injection, secrets
    • deps — Dependency vulnerabilities, outdated packages, license compliance
    • perf — Performance bottlenecks, N+1 queries, bundle size
    • all (default) — Run all audit types
  2. Run audits based on scope:

    Security audit — Use the Task tool to spawn the security-auditor agent:

    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
  3. 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.
    
  4. Suggest next steps: Recommend the top 3 actions to take based on findings.

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.

  1. 4d ago First seen · 56 lines · 14 tokens per session scan A 7ea95213b6f1

Subscribe to this mod's changes

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.