lex: Instructions file for Codex

AGENTS.md

lex AGENTS.md is an instructions file for Codex, OpenCode from SFHAJJI/lex. It costs 303 tokens per session, scanned A, original, Apache-2.0.

A set of repository instructions for working on the Lex V3 product code. It defines the starting branch, required documents, pull-request process, review evidence, and decision boundaries.

In plain words
What is it for?
Use it when planning or implementing Lex V3 changes, preparing a pull request, recording test evidence, updating status files, and handling review or owner decisions.
Why use it?
It gives coding agents a shared procedure for making changes safely in this repository. It helps prevent work on the wrong branch or changes based on assumed product, legal, or business decisions.

Instructions file for CodexOpenCode

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

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

Reuse

Borrowing it

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

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

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/sfhajji/lex/agents-md"><img src="https://agentmods.dev/badge/instructions/sfhajji/lex/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 303 This file is loaded in full into every session.
When invoked 303 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.00303 $0.00303
Opus 5.5 $0.00121 $0.00121
Sonnet 5.5 $0.00061 $0.00061
Haiku 4.5 $0.00030 $0.00030

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

Security

Grade A, and why

lex 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 10d 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 · 23 lines

What it actually says

Lex V3 boot

This repository is the Lex V3 product code. Work starts from v3/integration; main is the legacy line.

Read, in this order, and nothing else before working:

  1. STATUS.md: the heads and the owner's pending decisions, and through it your lane's file (STATUS-WEB.md or STATUS-DATA.md): what is served, what is next, what is blocked.
  2. LAUNCH-CONTRACT.md: the acceptance checklist for the V3 launch.

Working rules:

  • Day-sized vertical slices on a branch from v3/integration; one pull request per slice.
  • Evidence in the pull request description: the commands run, the counts, the scope.
  • One fresh-context review per pull request. Findings must be material and reproduced. One repair round, then merge.
  • Update your lane's status file (STATUS-WEB.md or STATUS-DATA.md) in the same pull request; STATUS.md changes only for the heads and the owner's items.
  • Owner decisions (product scope, legal or public claims, publisher traffic, credentials, money) are asked in the pull request or at the weekly checkpoint, never assumed.
  • https://github.com/SFHAJJI/lex-governance holds the immutable specification pack and Decisions 82 to 93, which still describe product scope. Its working model and stage protocol are retired.
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. 10d ago First seen · 23 lines · 303 tokens per session scan A fc9d3f7ab48d

Subscribe to this mod's changes

lex AGENTS.md is an instructions file published in the GitHub repository SFHAJJI/lex (9 stars, last pushed 7d ago), licensed Apache-2.0. It adds 303 tokens to every session, about $0.0012 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-10-28.

Related

lex AGENTS.md compared with instructions from other repositories

lex AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
lex AGENTS.mdSFHAJJI/lexInstructions file97d agoApache-2.0A303Codex, OpenCode
plan-forge dapr.instructions.mdsrnichols/plan-forgeInstructions file62d agoMITA4,975GitHub Copilot
plan-forge database.instructions.mdsrnichols/plan-forgeInstructions file62d agoMITA1,890GitHub Copilot
plan-forge naming.instructions.mdsrnichols/plan-forgeInstructions file62d agoMITA1,453GitHub Copilot
plan-forge caching.instructions.mdsrnichols/plan-forgeInstructions file62d agoMITA733GitHub Copilot
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143ktodayMITA7,461Codex, OpenCode