repo2agent: Instructions file for Codex

AGENTS.md

repo2agent AGENTS.md is an instructions file for Codex, OpenCode from Sanmu-27/repo2agent. It costs 312 tokens per session, scanned A, original, MIT.

Repository instructions for AI coding agents working on the repo2agent project, including its files, commands, and workflow.

In plain words
What is it for?
Use them when an agent edits repo2agent, runs its tests or linter, or needs to follow its repository map and safety rules.
Why use it?
They give an agent project-specific guidance so it can inspect the right files, keep changes focused, and verify its work safely.

Instructions file for CodexOpenCode

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

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

Reuse

Borrowing it

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

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

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/sanmu-27/repo2agent/agents-md"><img src="https://agentmods.dev/badge/instructions/sanmu-27/repo2agent/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 312 This file is loaded in full into every session.
When invoked 312 The same file — it is already loaded in full.
Security scan A 0 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.00312 $0.00312
Opus 5 $0.00156 $0.00156
Sonnet 5 $0.00062 $0.00062
Haiku 4.5 $0.00031 $0.00031

Measured 8d ago against content hash adca0eaae001, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

repo2agent 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 8d 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.

AGENTS.md · 50 lines

What it actually says

AGENTS.md

This file was generated by repo2agent. It gives AI coding agents the shortest reliable path to work safely in this repository.

Repository Snapshot

  • Name: repo2agent
  • Stack: Not detected
  • Package manager: npm

Project Map

  • lib/
  • test/
  • docs/
  • examples/
  • .npm-cache/
  • bin/
  • scripts/

Common Commands

  • test: npm run test
  • lint: npm run lint

Agent Workflow

  • Read the relevant files before editing.
  • Prefer existing patterns, naming, and architecture over new abstractions.
  • Keep changes scoped to the user request.
  • Do not rewrite unrelated code or reformat files outside the change.
  • Do not discard local/user changes without explicit permission.
  • Update tests when behavior changes.
  • Run the smallest meaningful verification command before finalizing.
  • In the final response, say what changed, what was verified, and what risk remains.

Safety Rules

  • Be careful with secrets, auth, permissions, payments, migrations, generated files, and lockfiles.
  • Avoid adding dependencies unless they clearly reduce complexity.
  • If a command fails, report the failure and choose the next most useful verification step.

Codex Notes

  • Use fast search tools such as rg where available.
  • Make manual edits with the repository's normal editing flow.
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. 8d ago First seen · 50 lines · 312 tokens per session scan A adca0eaae001

Subscribe to this mod's changes

repo2agent AGENTS.md is an instructions file published in the GitHub repository Sanmu-27/repo2agent (1 stars, last pushed 4mo ago), licensed MIT. It adds 312 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-08-31.

Related

Other instructions, from other repositories

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,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,153 tokens

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 · 6,785 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, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 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,469 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens