Borrowing it
Nothing to install: this file belongs to morluto/leantoken. 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/morluto/leantoken/main/AGENTS.mdgit clone --depth 1 https://github.com/morluto/leantokenWrote 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/morluto/leantoken/agents-md)<a href="https://agentmods.dev/instructions/morluto/leantoken/agents-md"><img src="https://agentmods.dev/badge/instructions/morluto/leantoken/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.
<a href="https://agentmods.dev/instructions/morluto/leantoken/agents-md"><img src="https://agentmods.dev/badge/instructions/morluto/leantoken/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.00529 | $0.00529 |
| Opus 5.5 | $0.00212 | $0.00212 |
| Sonnet 5.5 | $0.00106 | $0.00106 |
| Haiku 4.5 | $0.00053 | $0.00053 |
Grade A, and why
leantoken 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 14d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository guidance
LeanToken is a Rust application and library providing token-bounded repository retrieval through CLI and MCP adapters.
Architecture
Servicesowns application behavior; CLI and MCP adapters remain thin.- Preserve deterministic ranking, exact token budgets, bounded memory, atomic SQLite generations, and request snapshot consistency.
- Document new scan, fan-out, storage, and concurrency bounds in
docs/architecture.md.
Development
Local tests use disposable fixtures and have no production access. Run relevant
checks, fix change-caused failures, and rerun affected tests without asking for
approval. Before the first push, format the tree and run a behavioral check that
proves the change; the complete CI suite need not block opening a pull request.
Use cargo test-focused <module-or-test> to filter the library, binary, and
integration targets, and use the ownership map in docs/development.md when
choosing affected tests.
GitHub Actions owns normal Rust merge readiness and must pass:
cargo fmt --all -- --check
cargo clippy --all-targets --all-features -- -D warnings
cargo test-product
It also runs cargo test-extras for examples and benchmark behavior and checks
rustdoc for public APIs and documentation. Run a complete gate locally only
when reproducing CI, working without CI, or changing the gate itself. See
docs/development.md for the complete development, packaging, and release
workflow.
Change-specific validation
- For performance investigations,
$optimize-accuracy-firstpoints to the repository's measurement tools. Ordinary retrieval fixes do not need a performance study or paired agent evaluation. - For storage changes, include query-plan evidence and focused integration tests; a faster microbenchmark does not justify weaker atomicity, limits, freshness, or deterministic results.
- Treat MCP schema snapshots as protocol changes. Inspect the schema diff before
accepting an
instaupdate. - Prioritize real-binary E2E tests, then integration tests across component boundaries, then golden tests grounded in real data. Keep a private unit test only when it proves a consequential invariant that these layers cannot reasonably exercise. Prune implementation mirrors and redundant checks.
- Match surrounding Rust naming, documentation, and comment conventions.
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.
- 14d ago Changed · +2 lines · +41 tokens per session 3b71d42f5785
- 1mo ago Changed · +3 lines · +42 tokens per session c90831798302
- 1mo ago First seen · 54 lines · 446 tokens per session scan A 4cb3f36be7b8
leantoken AGENTS.md is an instructions file published in the GitHub repository morluto/leantoken (120 stars, last pushed 2d ago), licensed Apache-2.0. It adds 529 tokens to every session, about $0.0021 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.
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).
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.
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).
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 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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.