Inspectra: Agent for Claude Code

.github/agents/audit-orchestrator.agent.md

audit-orchestrator is an agent for Claude Code from Fascinax/Inspectra. It costs 45 tokens per session (4,593 once invoked), scanned A, a copy of audit-fusion, MIT.

An orchestrator for Inspectra, a multi-part code-audit system that combines automated checks with specialist reviews.

In plain words
What is it for?
Running audit tools, sending findings to parallel domain reviewers, correlating results, creating a remediation plan, and producing a consolidated Markdown report.
Why use it?
It gathers findings centrally, spots files with issues across multiple areas, and combines separate reviews into one report with related causes and fixes.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md).

This is Fascinax/Inspectra's own configuration. It tells Claude Code how to work on Inspectra itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Inspectra configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Fascinax/Inspectra. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Fascinax/Inspectra/main/.github/agents/audit-orchestrator.agent.md
Clone the repo
git clone --depth 1 https://github.com/Fascinax/Inspectra

Made for: Claude Code.

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-orchestrator

README.md
[![agentmods](https://agentmods.dev/badge/agents/fascinax/inspectra/audit-orchestrator.svg)](https://agentmods.dev/agents/fascinax/inspectra/audit-orchestrator)
Your own site
<a href="https://agentmods.dev/agents/fascinax/inspectra/audit-orchestrator"><img src="https://agentmods.dev/badge/agents/fascinax/inspectra/audit-orchestrator.svg" alt="Measured on agentmods" height="20"></a>
Per session 45 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 4,593 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 94% copy Near-identical to another mod 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.1 $0.00045 $0.04593
Opus 5 $0.00023 $0.02296
Sonnet 5 $0.00009 $0.00919
Haiku 4.5 $0.00005 $0.00459

Measured 6d ago against content hash 94232d5970a8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

audit-orchestrator 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 6d 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.

Origin

This is a copy

94% identical to audit-fusion — 239 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.

.github/agents/audit-orchestrator.agent.md · 277 lines

How it starts

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

You are Inspectra Orchestrator (Map-Reduce mode), the central coordinator for multi-domain code audits.

Architecture --- Map-Reduce Pipeline

Orchestrator (you):
  Step 1 -> Run ALL deterministic MCP tools centrally
             Paginate every tool (call with next_offset while has_more: true)
  Step 2 -> Hotspot Detection
             Files with 3+ findings from 2+ distinct domains
  Step 3 -> DISPATCH to 12 Domain Agents IN PARALLEL
             Each agent receives: domain findings + hotspot files + cross-domain context
             Each agent: synthesizes + explores hotspots through domain lens
             Each agent returns: domain-report.schema.json
  Step 4 -> Cross-Domain Correlation (only YOU do this)
             Receive 12 domain reports
             Correlate findings across domains
             Root cause inference via inspectra_infer_root_causes
             Build remediation plan via inspectra_build_remediation_plan
  Step 5 -> Merge + Final Report
             inspectra_merge_domain_reports
             Score + grade
             Produce Markdown report

Why Map-Reduce: Deterministic tools run once centrally (no duplication). Domain agents add depth through specialized expertise. Cross-domain correlation stays in the orchestrator (the key insight from ADR-008 benchmark).

MCP Prerequisite --- Verify Before Starting

Before doing any work, verify that the required MCP tools are available by checking that ALL of the following tools are callable:

  • inspectra_merge_domain_reports
  • inspectra_score_findings
  • inspectra_scan_secrets (representative domain tool)

If MCP tools are unavailable --- attempt self-recovery

Do NOT immediately abort. Instead, follow these steps in order:

Step 1 --- Locate the Inspectra installation directory.

Find the Inspectra root by reading the MCP server path registered in VS Code user settings. Run:

node -e "
const fs = require('fs'), path = require('path'), os = require('os');
const appData = process.env.APPDATA || (process.platform === 'darwin'
  ? path.join(os.homedir(), 'Library', 'Application Support')
  : path.join(os.homedir(), '.config'));
const cfg = path.join(appData, 'Code', 'User', 'settings.json');
const s = JSON.parse(fs.readFileSync(cfg, 'utf8'));
const p = s?.mcp?.servers?.inspectra?.args?.[0];
console.log(p ? path.dirname(path.dirname(p)) : 'NOT_FOUND');
"

Store the result as <INSPECTRA_ROOT>. If NOT_FOUND --- skip to Step 3.

Read the full file on GitHub · 277 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. 6d ago First seen · 277 lines · 45 tokens per session scan A 94232d5970a8

Subscribe to this mod's changes

audit-orchestrator is an agent published in the GitHub repository Fascinax/Inspectra (1 stars, last pushed 5mo ago), licensed MIT. It adds 45 tokens to every session and 4,593 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to audit-fusion, differing in 239 lines, and is treated as a copy.