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/spencermarx/open-code-review/agents-mdgit clone --depth 1 https://github.com/spencermarx/open-code-reviewWrote 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/spencermarx/open-code-review/agents-md)<a href="https://agentmods.dev/instructions/spencermarx/open-code-review/agents-md"><img src="https://agentmods.dev/badge/instructions/spencermarx/open-code-review/agents-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 | $0.00323 | $0.00323 |
| Opus 5 | $0.00161 | $0.00161 |
| Sonnet 5 | $0.00065 | $0.00065 |
| Haiku 4.5 | $0.00032 | $0.00032 |
Grade A, and why
open-code-review AGENTS.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 yesterday.
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.
What it actually says
OpenSpec Instructions
These instructions are for AI assistants working in this project.
Always open @/openspec/AGENTS.md when the request:
- Mentions planning or proposals (words like proposal, spec, change, plan)
- Introduces new capabilities, breaking changes, architecture shifts, or big performance/security work
- Sounds ambiguous and you need the authoritative spec before coding
Use @/openspec/AGENTS.md to learn:
- How to create and apply change proposals
- Spec format and conventions
- Project structure and guidelines
Keep this managed block so 'openspec update' can refresh the instructions.
Code Conventions
See CLAUDE.md for canonical code conventions
Open Code Review Instructions
These instructions are for AI assistants handling code review in this project.
Always open .ocr/skills/SKILL.md when the request:
- Asks for code review, PR review, or feedback on changes
- Mentions "review my code" or similar phrases
- Wants multi-perspective analysis of code quality
- Asks to map, organize, or navigate a large changeset
Use .ocr/skills/SKILL.md to learn:
- How to run the 8-phase review workflow
- How to generate a Code Review Map for large changesets
- Available reviewer personas and their focus areas
- Session management and output format
Keep this managed block so ocr init can refresh the instructions.
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.
- yesterday First seen · 44 lines · 323 tokens per session scan A e2918508f248
open-code-review AGENTS.md is an instructions file published in the GitHub repository spencermarx/open-code-review (353 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 323 tokens to every session, about $0.0016 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-09-03.
Other instructions, from other repositories
embedded-systems-architect AGENTS.md
Instructions for Zachariah9420/embedded-systems-architect: This repository ships an agent skill for embedded-systems and edge-AI development work.
pbnz-skills AGENTS.md
AGENTS.md instructions for PBNZ/pbnz-skills, covering agents.md — pbnz-skills, start-here map — where things live and ground rules.
qa-orchestra CLAUDE.md
Claude Code instructions for Anasss/qa-orchestra, covering qa orchestra — claude code instructions, what this project is, quick start, 1. clone into your workspace and 2. fill in your project context.
agent-skills CLAUDE.md
Instructions for mindbox-cloud/agent-skills, covering agent-skills — developer guide for claude code, repository purpose, repository structure, how to add a new plugin and step 1 — create the directory structure.
claude-sdlc CLAUDE.md
Claude Code instructions for lantisprime/claude-sdlc, covering claude.md, what this repo is, design intent — read this before "improving" anything, eat your own dog food and hook strictness philosophy.
claude-account-switch AGENTS.md
AGENTS.md instructions for LightZirconite/claude-account-switch, covering claude + codex account switch - agent guide, product invariants, authentication ux, switching safety and provider parity and deliberate differences.