cpv-batch-security-audit

cpv-batch-security-audit is a command for coding agents from Emasoft/claude-plugins-validation. It costs 111 tokens per session (2,077 once invoked), scanned A, original, MIT.

A command for running security checks across every plugin in a marketplace, a selected list, or one plugin. A marketplace is a collection of plugins that users can install.

In plain words
What is it for?
Use it to audit plugins from local paths, GitHub URLs, marketplace locations, lists, or list files, with several checks running in parallel.
Why use it?
It gives maintainers one security report for many plugins without checking each one manually. It runs only the security checks, making the audit more focused than full plugin validation.

Command

Part of the claude-plugins-validation plugin — 31 skills, 14 commands, 14 agents 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/emasoft/claude-plugins-validation/cpv-batch-security-audit
Clone the repo
git clone --depth 1 https://github.com/Emasoft/claude-plugins-validation

Or install claude-plugins-validation, the plugin that ships this one along with the rest of its 31 skills, 14 commands, 14 agents.

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 cpv-batch-security-audit

README.md
[![agentmods](https://agentmods.dev/badge/commands/emasoft/claude-plugins-validation/cpv-batch-security-audit.svg)](https://agentmods.dev/commands/emasoft/claude-plugins-validation/cpv-batch-security-audit)
Your own site
<a href="https://agentmods.dev/commands/emasoft/claude-plugins-validation/cpv-batch-security-audit"><img src="https://agentmods.dev/badge/commands/emasoft/claude-plugins-validation/cpv-batch-security-audit.svg" alt="Measured on agentmods" height="20"></a>
Per session 111 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,077 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.00111 $0.02077
Opus 5 $0.00056 $0.01038
Sonnet 5 $0.00022 $0.00415
Haiku 4.5 $0.00011 $0.00208

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

Security

Grade A, and why

cpv-batch-security-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 3d 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.

commands/cpv-batch-security-audit.md · 220 lines

How it starts

The opening of the file, as written. The whole thing — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/cpv-batch-security-audit — Security audit every plugin in a marketplace

For users who maintain a marketplace and need a fleet-wide security snapshot, this command dispatches one cpv-plugin-validator-agent per plugin in batch_security_audit mode. The agent runs only the validate_security checker (faster than full plugin validation, and covers the most important signal: external CC-Audit / Tirith / TruffleHog / Semgrep / Cisco AI Defense / in-process rule findings).

Same input grammar and dispatch shape as /cpv-batch-validate — single plugin / single plugin URL / marketplace local / marketplace URL / list / @listfile / comma-separated.

You are the orchestrator

You — the model running THIS turn — orchestrate the batch from the main session. You do NOT scan anything yourself.

Step 0 — Resolve arguments

The user supplies a target spec (required; first positional — accepts every shape listed above) plus an optional --max-parallel N (default 8, cap 16).

If no target was given, ask plain-text:

Which marketplace, plugin, or list should I security-audit? Provide a path, URL, or @listfile.

Step 1 — Build the batch plan

# Separate the positional target specs from the --max-parallel flag in a
# single pass. We must NOT collapse to "$1": the input grammar above lists
# a whitespace-separated LIST (`./a ./b ./c`) as a valid shape, and the
# orchestrator's `plan` subcommand declares its inputs as `nargs="+"`, so
# every positional must be forwarded — using only "$1" would silently
# audit the first plugin and drop the rest.
#
# Both --max-parallel N (two tokens) and --max-parallel=N (one token) are
# handled, because argparse accepts the `=` form and a user may type it.
# Default 8; the orchestrator re-caps at 16, so a larger N is safe to pass.
BATCH_SPECS=()
MAX_PARALLEL=8
while [ "$#" -gt 0 ]; do
  case "$1" in
    --max-parallel)
      MAX_PARALLEL="$2"
      shift 2
      ;;
    --max-parallel=*)
      MAX_PARALLEL="${1#--max-parallel=}"
      shift
      ;;
    *)
      BATCH_SPECS+=("$1")
      shift
      ;;
  esac
done

if [ "${#BATCH_SPECS[@]}" -eq 0 ]; then
  echo "ERROR: no target spec given to /cpv-batch-security-audit" >&2
  exit 1
fi

python3 "${CLAUDE_PLUGIN_ROOT}/scripts/cpv_batch_orchestrator.py" plan \
  "${BATCH_SPECS[@]}" \
  --agent cpv-plugin-validator-agent \
  --mode batch_security_audit \
  --max-parallel "$MAX_PARALLEL"

Read the full file on GitHub · 220 lines

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. 3d ago First seen · 220 lines · 111 tokens per session scan A 60d5fec7bc32

Subscribe to this mod's changes

cpv-batch-security-audit is a command published in the GitHub repository Emasoft/claude-plugins-validation (4 stars, last pushed 5d ago), licensed MIT. It adds 111 tokens to every session and 2,077 once invoked, about $0.0006 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.