GraphEngineering: Instructions file for Codex

AGENTS.md

GraphEngineering AGENTS.md is an instructions file for Codex, OpenCode from reacher-z/GraphEngineering. It costs 284 tokens per session, scanned A, original, MIT.

Repository instructions for GraphEngineering that define product rules, file ownership during parallel work, and required verification.

In plain words
What is it for?
Use them when changing GraphEngineering code, especially the shared protocol in `spec/`, runtime packages, platform tools, documentation, or tests.
Why use it?
They help contributors keep the TypeScript and Python implementations aligned, preserve structured failures, avoid unsafe graph behavior, and prevent edits from crossing ownership boundaries.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

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

Reuse

Borrowing it

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

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

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/reacher-z/graphengineering/agents-md"><img src="https://agentmods.dev/badge/instructions/reacher-z/graphengineering/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 284 This file is loaded in full into every session.
When invoked 284 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.00284 $0.00284
Opus 5 $0.00142 $0.00142
Sonnet 5 $0.00057 $0.00057
Haiku 4.5 $0.00028 $0.00028

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

Security

Grade A, and why

GraphEngineering 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 11d 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 · 29 lines

What it actually says

Repository agent guidance

Product invariants

  • spec/ is the canonical cross-language protocol source.
  • TypeScript and Python behavior must stay aligned through conformance fixtures.
  • Failures are structured values or events; never silently replace them with null.
  • Deterministic transforms handle plumbing; model nodes handle judgment.
  • Implicit graph cycles, unbounded retries, and unbounded dynamic fan-out are invalid.
  • External side effects are at-least-once and require idempotency or approval.
  • Telemetry and prompt/response capture are off by default.

Ownership during parallel work

  • Main/integration agent owns root configuration, spec/, codex_plans/, and codex_logs/.
  • TypeScript runtime work owns packages/core/ and packages/runtime/.
  • Python runtime work owns python/.
  • Platform work owns packages/cli/, packages/mcp-server/, apps/, tools/, docs/, and examples/ when assigned.

Do not edit another lane's files without an explicit handoff. Preserve unrelated changes in the shared worktree.

Verification

  • Run focused tests for every changed package.
  • Public behavior requires tests and documentation.
  • Never run a rewriting formatter across files owned by another task.
  • Real model-provider tests are opt-in; normal tests use deterministic fakes.
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. 11d ago First seen · 29 lines · 284 tokens per session scan A 1f679acab092

Subscribe to this mod's changes

GraphEngineering AGENTS.md is an instructions file published in the GitHub repository reacher-z/GraphEngineering (4 stars, last pushed today), licensed MIT. It adds 284 tokens to every session, about $0.0014 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

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

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

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