code: Instructions file for Codex

AGENTS.md

code AGENTS.md is an instructions file for Codex, OpenCode from cbusillo/code. It costs 3,952 tokens per session, scanned A, original, Apache-2.0.

A repository instruction file for Every Code, a coding product and command-line tool. It defines naming, documentation, workflow, and upstream-source rules.

In plain words
What is it for?
Use it when an agent changes Every Code code, docs, user interfaces, workflows, or commits.
Why use it?
It prevents inconsistent product names and helps agents follow the repository's release, import, and documentation conventions.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: reads ~/.codex paths; mentions Codex.

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

Not installable: its command points at a path on the author’s own machine, so it runs nowhere else. The line is /home/azureuser/.bashrc.

Reuse

Borrowing it

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

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

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/cbusillo/code/agents-md"><img src="https://agentmods.dev/badge/instructions/cbusillo/code/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 3,952 This file is loaded in full into every session.
When invoked 3,952 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.03952 $0.03952
Opus 5.5 $0.01581 $0.01581
Sonnet 5.5 $0.00790 $0.00790
Haiku 4.5 $0.00395 $0.00395

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

Security

Grade A, and why

code 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 2mo 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 · 243 lines

How it starts

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

Every Code Repository Guidance

Repo workflow metadata lives in .github/github.json; keep that file aligned with branch roles, validation gates, GitHub signal capabilities, workflow names, PR/release policy, docs routing, and local cleanup policy when those facts change.

Every Code is the product in this repository; code is the command users type. Use Every Code for the product name in prose, docs, UI copy, issue text, release text, and first mentions. Use Every Code CLI for the product CLI surface, and the code command when referring to the executable. Use the Every Code agent for the assistant identity; Code is only a short display name after Every Code context is established. Use Every Code harness for the runtime/session wrapper that we restart and dogfood, and Every Code runtime for process/session/tool-execution internals.

Upstream import sources are just-every/code and openai/codex. Treat just-every/code as a fork upstream/import source. Treat openai/codex / Codex CLI as the original/direct upstream and provenance source. The current product architecture is Codex CLI as the substrate with Every Code layered on top. Locally, codex-rs is a read-only mirror of openai/codex:main; edit Rust sources under code-rs, the Every Code product workspace built on the Codex CLI substrate.

CODE_HOME / ~/.code are the primary config and state locations. CODEX_HOME / ~/.codex are compatibility fallbacks. Keep CODEX_* names when they are part of external, backend, or upstream compatibility; add CODE_* aliases or rename only through a scoped migration. See docs/upstream-import-policy.md#code-and-codex-compatibility-policy before changing environment variable behavior.

Rust implementation lives under code-rs:

  • Crate names are ownership markers. Imported Codex substrate crates may keep their upstream codex-* names only when they remain compatibility-critical or mostly upstream-shaped. Every Code-owned crates and new product-layer crates should use code-* names unless a documented external compatibility contract requires the upstream spelling.
  • When using format! and you can inline variables into {}, always do that.
  • Treat codex-rs as a read-only mirror of openai/codex:main; edit Rust sources under code-rs, including imported Codex-based sources that become part of the Every Code product workspace.
  • When aligning with upstream, prefer moving code-rs closer to current Codex CLI shapes and adding Every Code behavior as a small product-layer overlay. Do not make codex-rs mirror Every Code or edit it directly.

Completion/build step

  • Always validate using ./build-fast.sh from the repo root. This is the single required check and must pass cleanly.
  • ./build-fast.sh can take 20+min to run from a cold cache!!! Please use long timeout when running ./build-fast.sh or waiting for it to complete.
  • Policy: All errors AND all warnings must be fixed before you’re done. Treat any compiler warning as a failure and address it (rename unused vars with _, remove mut, delete dead code, etc.).
  • Do not run additional format/lint/test commands on completion (e.g., just fmt, just fix, cargo test) unless explicitly requested for a specific task.
  • NEVER run rustfmt
  • Before release-bound work lands on main, run ./pre-release.sh to mirror the release preflight (dev-fast build, CLI smokes, workspace nextest).

Optional regression checks (recommended when touching the Rust workspace):

  • cargo nextest run --no-fail-fast — runs all workspace tests with the TUI helpers automatically enabled. The suite is green after the resume fixtures/git-init fallback updates; older Git builds may print a warning when falling back from --initial-branch, but tests still pass.
  • Focused sweeps stay quick and green: cargo test -p code-tui --features test-helpers, cargo test -p code-cloud-tasks --tests, and cargo test -p mcp-types --tests.

When debugging regressions or bugs, write a failing test (or targeted reproduction script) first and confirm it captures the issue before touching code—if it can’t fail, you can’t be confident the fix works.

Read the full file on GitHub · 243 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. 2mo ago First seen · 243 lines · 3,952 tokens per session scan A 674fd72368cd

Subscribe to this mod's changes

code AGENTS.md is an instructions file published in the GitHub repository cbusillo/code (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 3,952 tokens to every session, about $0.0158 per session on Opus 5.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

code AGENTS.md compared with instructions from other repositories

code AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
code AGENTS.mdcbusillo/codeInstructions file22mo agoApache-2.0A3,952Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143ktodayMITA7,461Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA5,649GitHub Copilot
langchain AGENTS.mdlangchain-ai/langchainInstructions file149ktodayMITA4,680Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA3,093GitHub Copilot
vscode model-prompts.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA2,022GitHub Copilot