code-review-graph: Instructions file for Codex

AGENTS.md

code-review-graph AGENTS.md is an instructions file for Codex, OpenCode from tirth8205/code-review-graph. It costs 1,120 tokens per session, scanned C, original, MIT.

Project instructions stored in an AGENTS.md file for the code-review-graph project. They explain the project's issue-tracking commands and safe, non-interactive shell usage.

In plain words
What is it for?
They help agents find available work, claim and close issues, push issue data, and use explicit file-operation flags.
Why use it?
They give coding agents the project-specific rules needed to work consistently and avoid commands that wait for confirmation.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions CLAUDE.md; names the TodoWrite tool.

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

About the project

code-review-graph is a local-first code intelligence graph that builds a persistent structural map of a codebase and supplies relevant context to AI coding tools through MCP and a CLI. It is used for code review and large-repository workflows, with catalogue add-ons providing integrations and instructions for operating it.

tirth8205/code-review-graph · 32,411 stars · on GitHub · code-review-graph.com

Reuse

Borrowing it

Nothing to install: this file belongs to tirth8205/code-review-graph. 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/tirth8205/code-review-graph/staging/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/tirth8205/code-review-graph

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 code-review-graph AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/tirth8205/code-review-graph/agents-md/github.svg)](https://agentmods.dev/instructions/tirth8205/code-review-graph/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/tirth8205/code-review-graph/agents-md"><img src="https://agentmods.dev/badge/instructions/tirth8205/code-review-graph/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 code-review-graph AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/tirth8205/code-review-graph/agents-md"><img src="https://agentmods.dev/badge/instructions/tirth8205/code-review-graph/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,120 This file is loaded in full into every session.
When invoked 1,120 The same file — it is already loaded in full.
Security scan C 1 finding. 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.01120 $0.01120
Opus 5.5 $0.00448 $0.00448
Sonnet 5.5 $0.00224 $0.00224
Haiku 4.5 $0.00112 $0.00112

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

Security

Grade C, and why

code-review-graph AGENTS.md scanned grade C with 1 finding 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.

rm -rf directory
AGENTS.md · 111 lines

How it starts

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

Agent Instructions

Project context (architecture, commands, conventions, tests) is in CLAUDE.md. This file holds the rules for every coding agent working in this repository.

Non-Interactive Shell Commands

cp, mv and rm may be aliased with -i on some systems, which leaves an agent waiting for a y/n answer that never comes. Always pass the non-interactive flag:

cp -f source dest
mv -f source dest
rm -f file
rm -rf directory
cp -rf source dest

Other commands that may prompt: scp and ssh (-o BatchMode=yes), apt-get (-y), brew (HOMEBREW_NO_AUTO_UPDATE=1).

Beads Issue Tracker

This project uses bd (beads) for issue tracking. Run bd prime to see full workflow context and commands.

Quick Reference

bd ready              # Find available work
bd show <id>          # View issue details
bd update <id> --claim  # Claim work
bd close <id>         # Complete work

Rules

  • Use bd for ALL task tracking — do NOT use TodoWrite, TaskCreate, or markdown TODO lists
  • Run bd prime for detailed command reference and session close protocol
  • Use bd remember for persistent knowledge — do NOT use MEMORY.md files

Session Completion

When ending a work session, you MUST complete ALL steps below. Work is NOT complete until git push succeeds.

MANDATORY WORKFLOW:

  1. File issues for remaining work - Create issues for anything that needs follow-up
  2. Run quality gates (if code changed) - Tests, linters, builds
  3. Update issue status - Close finished work, update in-progress items
  4. PUSH TO REMOTE - This is MANDATORY:
    git pull --rebase
    bd dolt push
    git push
    git status  # MUST show "up to date with origin"
    
  5. Clean up - Clear stashes, prune remote branches
  6. Verify - All changes committed AND pushed
  7. Hand off - Provide context for next session

CRITICAL RULES:

  • Work is NOT complete until git push succeeds
  • NEVER stop before pushing - that leaves work stranded locally
  • NEVER say "ready to push when you are" - YOU must push
  • If push fails, resolve and retry until it succeeds

Read the full file on GitHub · 111 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 Changed · -20 lines · -160 tokens per session 82671de78dba
  2. 1mo ago First seen · 131 lines · 1,280 tokens per session scan C eebbaff51973

Subscribe to this mod's changes

code-review-graph AGENTS.md is an instructions file published in the GitHub repository tirth8205/code-review-graph (32,411 stars, last pushed 11d ago), licensed MIT. It adds 1,120 tokens to every session, about $0.0045 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

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,715 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,786 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

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens