lex: Instructions file for Claude Code

CLAUDE.md

lex CLAUDE.md is an instructions file for Claude Code from SFHAJJI/lex. It costs 438 tokens per session, scanned A, original, Apache-2.0.

A set of project instructions for working on Lex, a system for retrieving and checking Luxembourg law and reviewed European Union legal materials.

In plain words
What is it for?
It is for guiding coding agents in the Lex repository, enforcing safe file and credential handling, and preserving the project's build, deployment, and publishing conventions.
Why use it?
It keeps development and publishing work within the project's rules, including which data sources may be used and how sensitive information and repository changes are handled.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions Codex.

This is SFHAJJI/lex's own configuration. It tells Claude Code 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/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/SFHAJJI/lex

Made for: Claude Code.

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

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

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

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

Security

Grade A, and why

lex CLAUDE.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.

CLAUDE.md · 28 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 review per pull request by the other model family (Decision 95; this lane runs C:\lex-v3\lanes\review-by-codex.ps1 -Pr <n>). Findings must be material and reproduced. One repair round, then merge on green CI.
  • 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.
  • Keep OWNER-BRIEF.md current: the owner's one-page view, at most 40 lines of plain words and no hashes, updated in the first pull request of each day and whenever a run starts, ends or stops.
  • Owner decisions are money, legal or public claims, credentials and going live (the owner's standing order of 2026-09-30), plus the per-run publisher-traffic authorisations STATUS.md lists. They are asked in the pull request or at the weekly checkpoint, never assumed. Everything else the driver decides and records in its lane's status file as a reversible driver decision.
  • 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 Changed · -149 lines · -1,913 tokens per session 20b2235836af
  2. 2mo ago First seen · 177 lines · 2,351 tokens per session scan A 7ffa7ff4b6f3

Subscribe to this mod's changes

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

lex CLAUDE.md compared with instructions from other repositories

lex CLAUDE.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
lex CLAUDE.mdSFHAJJI/lexInstructions file97d agoApache-2.0A438Claude Code
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,516GitHub Copilot
langchain AGENTS.mdlangchain-ai/langchainInstructions file149ktodayMITA4,680Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file275k3d agoMITA4,313Codex, OpenCode