legax: Instructions file for Codex

AGENTS.md

legax AGENTS.md is an instructions file for Codex, OpenCode from zhanex/legax. It costs 690 tokens per session, scanned A, original, MIT.

Project rules for AI coding assistants working on Legax, a dependency-free Node.js application configured with YAML. They define how code, documentation, process coordination, MCP tools, and security boundaries must be handled.

In plain words
What is it for?
Guiding code changes, configuration edits, documentation updates, MCP integrations, process coordination, and reviews in the Legax repository.
Why use it?
They keep changes consistent with the project’s architecture and prevent unsafe shortcuts such as bypassing approval prompts or running arbitrary remote commands.

Instructions file for CodexOpenCode

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

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

View source ↗ zhanex/legax
Reuse

Borrowing it

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

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

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/zhanex/legax/agents-md"><img src="https://agentmods.dev/badge/instructions/zhanex/legax/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 690 This file is loaded in full into every session.
When invoked 690 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.00690 $0.00690
Opus 5.5 $0.00276 $0.00276
Sonnet 5.5 $0.00138 $0.00138
Haiku 4.5 $0.00069 $0.00069

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

Security

Grade A, and why

legax 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 · 50 lines

How it starts

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

AGENTS.md

English | Simplified Chinese

This is the repository instruction contract for AI coding agents working on Legax. Start here, then read Context For LLMs. Do not load every document by default.

Hard Rules

  • Keep the project dependency-free: Node 18+ standard library only, no bundler, and no new npm dependency unless the design has been accepted.
  • Keep configuration YAML-only. Use scripts/lib/yaml.mjs; do not add JSON config support or a YAML dependency casually.
  • Keep cross-process daemon and adapter coordination in scripts/lib/runtime-state.mjs; do not create sibling state files for cursors, selected sessions, modes, or launch requests.
  • Keep MCP as a capability layer. MCP tools may notify, poll, or request permission, but must not start or stop adapter processes.
  • Never simulate UI clicks, auto-approve native prompts, or bypass an agent's security policy.
  • Do not route remote workflow input to arbitrary shell, eval, script, prompt, command, or free-form executable args.
  • Keep documentation language pairs together: English .md with .zh-CN.md, and config.example*.yaml with matching config.example*.zh-CN.yaml.
  • Keep tracked documentation and commented examples UTF-8 without BOM; do not rewrite them through locale-dependent shell encodings.
  • Do not commit implementation plans, drafts, scratch notes, audit notes, or agent transcripts as tracked docs. Use ignored process directories or external task systems.
  • If you add a script or E2E file, append it to the explicit package.json check:node or test:e2e list.

Context Loading

  • Read docs/context_for_llms.md for the task routing table and canonical owners.
  • Default to English docs. Load .zh-CN pairs only for translation, Chinese documentation work, or pair consistency checks.
  • English docs are the canonical contract. Chinese docs are localized mirrors; if they diverge, follow English and update both.
  • For non-trivial code changes, use the smallest task-specific context set from docs/context_for_llms.md, then use docs/CHANGE_MATRIX.md for focused verification.
  • If docs conflict with this file, stop and surface the conflict before editing.

Read the full file on GitHub · 50 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 First seen · 50 lines · 690 tokens per session scan A e6b32b69c3f8

Subscribe to this mod's changes

legax AGENTS.md is an instructions file published in the GitHub repository zhanex/legax (11 stars, last pushed 4mo ago), licensed MIT. It adds 690 tokens to every session, about $0.0028 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-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,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,731 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,261 tokens