codexa: Instructions file for Claude Code

AGENTS.md

codexa AGENTS.md is an instructions file for Claude Code, Codex, OpenCode from mirnoorata/codexa. It costs 635 tokens per session, scanned A, original, MIT.

A project-specific instruction file for Codexa, covering development, startup, testing, and GitHub release procedures.

In plain words
What is it for?
It is for setting up Codexa, running its checks, managing dependencies and generated files, and following its change and release process.
Why use it?
It gives the coding agent the repository’s rules so it can work consistently and avoid committing local or private data.

Instructions file for Claude CodeCodexOpenCode

Written for Claude Code and Codex and OpenCode: SessionStart hook event, but also the file is AGENTS.md. Also seen: mentions Codex.

This is mirnoorata/codexa's own configuration. It tells Claude Code, Codex and OpenCode how to work on codexa 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 codexa configures →

Reuse

Borrowing it

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

Made for: Claude Code, 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 codexa AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/mirnoorata/codexa/agents-md"><img src="https://agentmods.dev/badge/instructions/mirnoorata/codexa/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 635 This file is loaded in full into every session.
When invoked 635 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.00635 $0.00635
Opus 5.5 $0.00254 $0.00254
Sonnet 5.5 $0.00127 $0.00127
Haiku 4.5 $0.00064 $0.00064

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

Security

Grade A, and why

codexa 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 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.

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 · 53 lines

How it starts

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

Codexa Project Kernel

Keep this automatic layer repository-local and compact. Detailed setup, recovery, architecture, and release procedures live in README.md and docs/; load them only when the task reaches that boundary.

Development

  • Restore locked dependencies with npm ci; use npm install only when deliberately changing dependencies and package-lock.json.
  • Run npm run check for the normal full gate.
  • Keep generated or host-local state out of Git: dist/, node_modules/, .codex/codebase/, .codex/cache/, local storage, config, and hooks are ignored. The tracked environment and bootstrap launchers are intentional.
  • Use deterministic public fixtures and placeholders such as /path/to/project, OWNER/REPO, and example.com. Do not commit private paths, projects, hosts, credentials, logs, or session memory.

Project Startup

  • In the desktop Codex composer, select this saved project, Worktree, the intended starting branch, and the Codexa local environment before the first prompt. Mobile remote access may continue that chat but does not configure its local setup.
  • Adopt the app-created linked worktree; never create a second checkout for the same task. Attach a named branch before committing if the app starts detached, and leave app-managed cleanup to the app.
  • The tracked Bash and PowerShell launchers delegate to one serialized Node bootstrap. Generate dependencies, build output, core wiring, and the index in the active worktree; never copy machine-local config, hooks, indexes, or absolute launch commands from another checkout.
  • Setup proof is the immutable blob behind the per-worktree refs/worktree/codexa/bootstrap-receipt ref. SessionStart validates its durable subset; worktree-receipt validate --scope adoption additionally binds generated runtime/dependencies for a trusted shared controller, and the default full scope is the completion gate. A receipt never authorizes executing unvalidated worktree output.
  • Missing, stale, or invalid setup evidence is source-ready, not edit-ready. Follow README Codex Project Worktrees And Local Setup for repair. Neither config nor a receipt proves current-thread MCP activation.

Read the full file on GitHub · 53 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 · +6 tokens per session aba97c2c11ed
  2. 2mo ago First seen · 53 lines · 629 tokens per session scan A d52d760c11cf

Subscribe to this mod's changes

codexa AGENTS.md is an instructions file published in the GitHub repository mirnoorata/codexa (2 stars, last pushed 19d ago), licensed MIT. It adds 635 tokens to every session, about $0.0025 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

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,461 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,750 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