batch-audit

A command for auditing several functions in parallel, with attention to likely attack entry points and handlers at privilege boundaries. It produces one security report covering the individual findings and patterns across functions.

In plain words
What is it for?
Use it to audit top-ranked functions, RPC, COM, or WinRT handlers, named functions, or every method in a class, with optional limits on the number and risk level.
Why use it?
It speeds up reviews of a module or selected function set and makes related weaknesses easier to compare.

Command

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/marcosd4h/deepextractruntime/batch-audit
Clone the repo
git clone --depth 1 https://github.com/marcosd4h/DeepExtractRuntime
Per session 0 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,385 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.00000 $0.02385
Opus 5 $0.00000 $0.01192
Sonnet 5 $0.00000 $0.00477
Haiku 4.5 $0.00000 $0.00238

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

Security

Grade A, and why

batch-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 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.

commands/batch-audit.md · 218 lines

How it starts

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

Batch Audit

Overview

Security audit multiple functions in parallel, targeting the top-ranked attack surface entry points, module-scoped privilege-boundary handlers (RPC/COM/WinRT), or a user-specified list. Produces a consolidated security report with per-function audit summaries and cross-function patterns.

Usage:

  • /batch-audit appinfo.dll -- audit top 5 entry points (default)
  • /batch-audit appinfo.dll --top 10 -- audit top 10 entry points
  • /batch-audit appinfo.dll --top 10 --min-score 0.4 -- only entry points with attack score >= 0.4
  • /batch-audit appinfo.dll --privilege-boundary -- audit auto-discovered RPC/COM/WinRT handlers in the module
  • /batch-audit appinfo.dll --privilege-boundary --top 8 -- cap privilege-boundary auditing to the top 8 resolved handlers
  • /batch-audit appinfo.dll AiLaunchProcess AiCheckSecureApplicationDirectory AiCreateElevatedProcess -- audit specific functions
  • /batch-audit appinfo.dll --class CSecurityDescriptor -- audit all methods of a class

IMPORTANT: Execution Model

This is an execute-immediately command. Do NOT present anything for user confirmation. Run and write the final batch audit report straight to the chat as your response. The user expects to see the completed report.

Workspace Protocol

This command orchestrates N parallel audit workflows:

  1. Create .claude/workspace/<module>_batch_audit_<timestamp>/.
  2. Store per-function audit results in <run_dir>/<function_name>/results.json.
  3. Keep only severity summaries and top findings in context.
  4. Use <run_dir>/manifest.json to track which functions have been audited.

Execution Context

IMPORTANT: Any inline Python that imports helpers.* must run with cd <workspace>/.claude (so the .claude/ directory is on sys.path), not from the workspace root. Script invocations like python .claude/skills/.../script.py can be run from the workspace root because those scripts manage their own path setup.

Steps

Step 0: Preflight Validation

Read the full file on GitHub · 218 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. 2d ago First seen · 218 lines · 0 tokens per session scan A 28b344eb7689

Subscribe to this mod's changes

batch-audit is a command published in the GitHub repository marcosd4h/DeepExtractRuntime (20 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,385 tokens. 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.