inspectrum: Instructions file for Codex

AGENTS.md

inspectrum AGENTS.md is an instructions file for Codex, OpenCode from yannmenec/inspectrum. It costs 2,382 tokens per session, scanned C, original, MIT.

A project instruction guide for inspectrum, an MCP server that asks multiple AI coding tools to review a plan and records the results in Markdown. MCP is a standard way for AI assistants to call external tools.

In plain words
What is it for?
Use it when developing or reviewing inspectrum, especially when running its plan-review tool, building the TypeScript project, or running tests.
Why use it?
It explains the repository's purpose, supported scope, setup, development loop, and testing commands so contributors can work consistently.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: reads .claude/ paths; mentions .claude-plugin; mentions CLAUDE.md.

This is yannmenec/inspectrum's own configuration. It tells Codex and OpenCode how to work on inspectrum 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 inspectrum configures →

Reuse

Borrowing it

Nothing to install: this file belongs to yannmenec/inspectrum. 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/yannmenec/inspectrum/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/yannmenec/inspectrum

Made for: Codex, OpenCode.

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 inspectrum AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/yannmenec/inspectrum/agents-md/github.svg)](https://agentmods.dev/instructions/yannmenec/inspectrum/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/yannmenec/inspectrum/agents-md"><img src="https://agentmods.dev/badge/instructions/yannmenec/inspectrum/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for inspectrum AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/yannmenec/inspectrum/agents-md"><img src="https://agentmods.dev/badge/instructions/yannmenec/inspectrum/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 2,382 This file is loaded in full into every session.
When invoked 2,382 The same file — it is already loaded in full.
Security scan C 2 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.02382 $0.02382
Opus 5.5 $0.00953 $0.00953
Sonnet 5.5 $0.00476 $0.00476
Haiku 4.5 $0.00238 $0.00238

Measured 1mo ago against content hash 67c8337be430, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

inspectrum AGENTS.md scanned grade C with 2 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 1mo 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

- Never run `rm -rf`, `git push --force`, `git reset --hard`, `git branch -D`, or `npm publish` without explicit user confirmation.

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

- Wraps peer LLM CLIs via `child_process` (Claude / Codex / Gemini), aggregates
AGENTS.md · 143 lines

How it starts

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

Inspectrum

Universal MCP server for multi-LLM plan review today, plan + code-change review tomorrow. One tool, many reviewers, flat-Markdown session log.

Stack: TypeScript strict (ES2022, Node16 modules), Node ≥ 20, ESM, MCP SDK 1.29+, Zod v4. Distribution: npx inspectrum. License: MIT.

Target user: a solo dev or small team running multiple coding agents (Claude Code, Codex, Cursor, Gemini CLI) who wants to stop copy-pasting plans between them.

What this repo is

  • A single MCP server (src/server.ts) exposing one tool: review_plan.
  • Wraps peer LLM CLIs via child_process (Claude / Codex / Gemini), aggregates their findings, optionally runs a judge agent for consolidation, writes a flat-Markdown session log to ~/.inspectrum/sessions/<ts>__<id>/.
  • v0.1 = plan-only review. v0.2+ extends to code/PR review and more reviewer backends (Kimi, Qwen, Ollama, OpenRouter). Stay inside the current scope unless an ADR or PR explicitly opens a new surface.

Setup & dev loop

  • Install: npm install
  • Build: npm run build (tsc → dist/)
  • Dev: npm run dev (tsx loader, no build step)
  • Tests: npm test (Vitest)
  • Coverage: npm run test:coverage
  • Lint: npx eslint src/ (flat config, eslint.config.js)
  • Typecheck: npx tsc --noEmit
  • Pre-commit (lefthook): typecheck + lint + tests-with-coverage run automatically.

Repo map

  • src/server.ts — MCP entrypoint, stdio transport, registers review_plan.
  • src/schemas.ts — central Zod v4 schemas. All schemas live here, not per module.
  • src/config.ts — ~/.inspectrum/config.toml loader (@iarna/toml + Zod).
  • src/tool/review-plan.ts — orchestration, parallel reviewers, verdict aggregation, report assembly, session write.
  • src/reviewers/ — index.ts (factory) + claude.ts, codex.ts, gemini.ts (CLI wrappers) + health.ts (doctor) + common.ts (shared helpers).
  • src/judge/judge.ts — consolidation pass with validateJudgeInvariants.
  • src/hook/{state,render,plan-gate}.ts — ExitPlanMode plan gate: hash/state loop-protection, budgeted deny rendering, hook orchestration (inspectrum plan-gate; ADR-0002).
  • src/prompts/index.ts — REVIEWER_SYSTEM_PROMPT, JUDGE_SYSTEM_PROMPT as inline TS strings, NOT loaded from .md.
  • src/session/{store,resources}.ts — flat-file persistence + MCP resource exposure.
  • src/version.ts — single source for the package version (server metadata + CLI).
  • .claude-plugin/ + hooks/ + commands/ + scripts/plan-gate-shim.sh — Claude Code plugin; the repo doubles as its marketplace.
  • scripts/e2e-plan-gate.sh — headless plan-mode E2E harness (npm run e2e:gate).
  • tests/{contract,unit,e2e}/ — Vitest. Fixtures under tests/fixtures/. tests/integration/ is opt-in-only (INSPECTRUM_E2E_CODEX=1, real codex smoke — ADR-0002); broader integration remains deferred per ADR-0001.

Read the full file on GitHub · 143 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. 1mo ago First seen · 143 lines · 2,382 tokens per session scan C 67c8337be430

Subscribe to this mod's changes

inspectrum AGENTS.md is an instructions file published in the GitHub repository yannmenec/inspectrum (2 stars, last pushed 1mo ago), licensed MIT. It adds 2,382 tokens to every session, about $0.0095 per session on Opus 5.5. A static security scan graded it C with 2 findings (recursive force delete, runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,649 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,257 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,159 tokens