Borrowing it
Nothing to install: this file belongs to lehre-labs/llmsdottxt-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/lehre-labs/llmsdottxt-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/lehre-labs/llmsdottxt-mcpWrote 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.
[](https://agentmods.dev/instructions/lehre-labs/llmsdottxt-mcp/agents-md)<a href="https://agentmods.dev/instructions/lehre-labs/llmsdottxt-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/lehre-labs/llmsdottxt-mcp/agents-md.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.01430 | $0.01430 |
| Opus 5 | $0.00715 | $0.00715 |
| Sonnet 5 | $0.00286 | $0.00286 |
| Haiku 4.5 | $0.00143 | $0.00143 |
Grade A, and why
llmsdottxt-mcp 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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This is llmsdottxt-mcp. Before doing anything else, read pyproject.toml so you know what we're building.
1. Build Around ONE IDEA
Read @IDEA.md first. Every change must serve the thesis it states.
This project exists for one reason. @IDEA.md names it, along with the non-goals that bound it. Before any change:
- If the change doesn't serve the IDEA, it doesn't belong here -- say so.
- If it lands in a documented non-goal, stop and flag the conflict.
- If the IDEA itself is unclear or seems wrong for the request, surface that before coding -- don't silently reinterpret it.
2. Read the Context
Before writing any code, understand the user's request and the project's language.
- Read
@CONTEXT-MAP.mdand@CONTEXT.md-- they define what things are called. - If the term you need is missing, define it there before using it.
- If the user used the wrong term, use the canonical one and note the discrepancy.
- A wrong name in code is worse than a bug.
3. Think Before Coding
Don't assume. Don't hide confusion. Surface tradeoffs.
Before implementing:
- State your assumptions explicitly. If uncertain, ask.
- If multiple interpretations exist, present them -- don't pick silently.
- If a simpler approach exists, say so. Push back when warranted.
- If something is unclear, stop. Name what's confusing. Ask.
4. Simplicity First
Minimum code that solves the problem. Nothing speculative.
- No features beyond what was asked.
- No abstractions for single-use code.
- No "flexibility" or "configurability" that wasn't requested.
- No error handling for impossible scenarios.
- If you write 200 lines and it could be 50, rewrite it.
Ask yourself: "Would a senior engineer say this is overcomplicated?" If yes, simplify.
5. Surgical Changes
Touch only what you must. Clean up only your own mess.
When editing existing code:
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.
- 7d ago First seen · 140 lines · 1,430 tokens per session scan A c30a43df5bd7
llmsdottxt-mcp AGENTS.md is an instructions file published in the GitHub repository lehre-labs/llmsdottxt-mcp (1 stars, last pushed yesterday), licensed Apache-2.0. It adds 1,430 tokens to every session, about $0.0072 per session on Opus 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.
Other instructions, from other repositories
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.
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).
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.
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).
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.