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 instructions/fascinax/inspectra/claude-mdgit clone --depth 1 https://github.com/Fascinax/InspectraWrote 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/instructions/fascinax/inspectra/claude-md)<a href="https://agentmods.dev/instructions/fascinax/inspectra/claude-md"><img src="https://agentmods.dev/badge/instructions/fascinax/inspectra/claude-md.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.1 | $0.01500 | $0.01500 |
| Opus 5 | $0.00750 | $0.00750 |
| Sonnet 5 | $0.00300 | $0.00300 |
| Haiku 4.5 | $0.00150 | $0.00150 |
Grade A, and why
Inspectra CLAUDE.md 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Inspectra
Hybrid code audit system using MCP tools. Three audit architectures:
- Tier B (Hybrid): Default. Single-prompt workflow: deterministic tools across 12 domains, optional hotspot exploration, then merged scoring. Use
/audit. - Map-Reduce (Multi-Agent): Orchestrator runs tools centrally, dispatches to 12 specialized domain agents in parallel, then cross-domain correlation. Use
@audit-orchestrator. - Fusion (Maximum Recall): Combines Tier B synthesis + Map-Reduce dispatch in a single run. Tools run once, both analysis passes produce findings, cross-architecture deduplication ensures no noise. Use
@audit-fusion.
Quick Reference
npm install # install deps
npm run build # compile MCP server → mcp/dist/
npm test # 750+ tests (Vitest)
npm run lint # tsc --noEmit + ESLint
Project Structure
.github/prompts/—/audit,/audit-pr,/audit-domain, and benchmark entry points.github/agents/— 14 agent definitions: orchestrator + fusion + 12 domain agentsmcp/src/— MCP server (TypeScript, ES2022, Node 20+)tools/— domain tool implementations (one file per domain)register/— tool registration with input/output schemasmerger/— scoring engine, deduplication, mergepolicies/— YAML policy loader, scoring defaultsrenderer/— HTML, PDF, Markdown, SARIF, JSON renderersutils/— shared utilities (files, paths, project-config, finding-builder, shared-constants)
schemas/— JSON Schema 2020-12 contracts (finding, domain-report, consolidated-report)policies/— scoring-rules.yml, severity-matrix.yml, profiles/bin/init.mjs— CLI entry point (inspectra setup,inspectra setup --claude,inspectra setup --codex,inspectra init,inspectra doctor)
Architecture Rules
- Every MCP tool is prefixed
inspectra_and registered in aregister/*.tsfile - Tool functions live in
tools/*.ts, register files inregister/*.ts— keep them separate - All tool responses use
findingsResponse()orjsonResponse()fromregister/response.ts - Handler registration uses factory functions from
register/handler-factory.ts:createStandardHandler,createConfigHandler,createProfiledHandler - Input schemas use
STANDARD_INPUT_SCHEMAorPROFILED_INPUT_SCHEMAfromregister/schemas.ts - Shared constants (
MAX_SNIPPET_LENGTH,SUPPORTED_EXTENSIONS,TEST_INFRA_PATH) live inutils/shared-constants.ts - Use
FindingBuilderfromutils/finding-builder.tsfor constructing findings in tool functions - Findings must match
schemas/finding.schema.json— domain enum: security, tests, architecture, conventions, performance, documentation, tech-debt, accessibility, api-design, observability, i18n, ux-consistency - Finding IDs: tool-detected
001-499(source: "tool", confidence ≥ 0.8), LLM-detected501+(source: "llm", confidence ≤ 0.7) - Prefixes: SEC-, TST-, ARC-, CNV-, PRF-, DOC-, DEBT-, ACC-, API-, OBS-, INT-, UX-
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.
- 5d ago First seen · 86 lines · 1,500 tokens per session scan A c82227094db1
Inspectra CLAUDE.md is an instructions file published in the GitHub repository Fascinax/Inspectra (1 stars, last pushed 5mo ago), licensed MIT. It adds 1,500 tokens to every session, about $0.0075 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 instructions, from other repositories
skylos AGENTS.md
AGENTS.md instructions for duriantaco/skylos, covering agents.md, what this repo is, use the skylos skill, work safely and common commands.
skylos CLAUDE.md
Claude Code instructions for duriantaco/skylos, covering claude.md, what this repo is, install, use and skill for using skylos.
ai-engineering AGENTS.md
AGENTS.md instructions for arcasilesgroup/ai-engineering, covering how work happens here, the twelve rules, what this project is, the shape of the tree and the two contracts that must not bend.
laravel-auditor AGENTS.md
Instructions for MrPunyapal/laravel-auditor, covering laravel auditor, package conventions, quick commands and local skills.
goshipit CLAUDE.md
Instructions for Capta1nRaj/goshipit, covering goshipit - project instructions, sync rule (enforce after every change), how to count checks, git commits and package.json description format.
craftsman-marketplace CLAUDE.md
Claude Code instructions for gul-labs/craftsman-marketplace, covering claude.md, editing rules and design principles (non-negotiable).