Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/guffawaffle/lex/copilot-instructionsgit clone --depth 1 https://github.com/Guffawaffle/lexWhat 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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00661 | $0.00661 |
| Opus 5 | $0.00331 | $0.00331 |
| Sonnet 5 | $0.00132 | $0.00132 |
| Haiku 4.5 | $0.00066 | $0.00066 |
Grade C, and why
lex copilot-instructions.md scanned grade C with 1 finding 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 yesterday.
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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- This block is auto-generated by `lex instructions generate`. Do not edit manually. --> How it starts
The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Copilot Instructions for Lex
Lex Instructions
Use Lex Memory. Before starting work, run
lex recall "topic"to retrieve prior context.
Core Commands
lex recall "topic" # Retrieve relevant context before work
lex remember # Store context after completing work
lex timeline # View recent work history
lex check # Validate policy compliance
Key Principle
Lex is the constitution, not the government. Schemas, contracts, and memory are stable surfaces. Don't leak implementation details into them.
Quick Links
docs/FOUNDERS_NOTE.md— Philosophydocs/CONTRACT_SURFACE.md— Contract surface (v1)canon/policy/lexmap.policy.json— Module boundaries
Run lex recall for detailed guidance on any topic.
🔐 Admin Authority
Copilot agents have delegated --admin merge authority when local CI passes.
Run lex recall "admin authority" for conditions.
🎭 Behavioral Layer (LexSona)
Persona execution is handled by LexSona (separate package).
Lex provides the behavioral memory socket (recordCorrection, getRules).
For persona-based workflows, see LexSona documentation.
⚠️ Critical Rules
Run lex recall for detailed guidance on:
lex recall "git tests"— NO git commits in tests (GPG signing hangs)lex recall "sql safety"— Curated query modules only (see TROUBLESHOOTING.md "SQL Safety Violations")lex recall "ip boundary"— Lex never imports from lexrunner
SQL Safety Quick Reference:
- All
db.prepare()calls must be in curated query modules (seetest/sql-safety.test.ts) - If you get a SQL safety test failure, see
TROUBLESHOOTING.mdfor refactor examples - Never use string interpolation for SQL queries - always use parameterized queries
🏗️ TypeScript Composite Projects
This repo uses TypeScript project references (composite projects). When adding new .ts files:
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.
- yesterday First seen · 96 lines · 661 tokens per session scan C 97f835e85479
lex copilot-instructions.md is an instructions file published in the GitHub repository Guffawaffle/lex (0 stars, last pushed 3d ago), licensed MIT. It adds 661 tokens to every session, about $0.0033 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
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).
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.