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/lexmount/moli/agents-mdgit clone --depth 1 https://github.com/lexmount/moliWhat 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.00105 | $0.00105 |
| Opus 5 | $0.00053 | $0.00053 |
| Sonnet 5 | $0.00021 | $0.00021 |
| Haiku 4.5 | $0.00011 | $0.00011 |
Grade A, and why
moli 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 2d 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.
What it actually says
Before committing changes that modify Rust source code or Rust build metadata
(such as Cargo.toml, Cargo.lock, or rust-toolchain), run all of the
following from the repository root and ensure they pass:
cargo fmt --all
cargo clippy --workspace --all-targets --all-features -- -D warnings
cargo nextest run --no-fail-fast
These commands are not required when the change set contains no Rust source or Rust build metadata 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.
- 2d ago First seen · 13 lines · 105 tokens per session scan A e2b638cd66a1
moli AGENTS.md is an instructions file published in the GitHub repository lexmount/moli (1,603 stars, last pushed today), licensed Apache-2.0. It adds 105 tokens to every session, about $0.0005 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-30.
Other instructions, from other repositories
playwright-rust CLAUDE.md
Instructions for padamson/playwright-rust, covering claude.md, project, repository layout, skills (procedural reference) and documentation hierarchy.
apitap CLAUDE.md
Instructions for n1byn1kt/apitap, covering claude.md, using apitap as an mcp tool, commands, architecture and module map.
apitap copilot-instructions.md
Instructions for n1byn1kt/apitap, covering copilot instructions for apitap, build and test commands, high-level architecture and key repository conventions.
Scavenge CLAUDE.md
Claude Code instructions for aarohim24/Scavenge, covering claude.md, 0. role, 1. think before coding, 2. simplicity first and 3. surgical changes.
fanqie-publisher-skill AGENTS.md
Instructions for amm10090/fanqie-publisher-skill, covering fanqie-publisher-skill — codex cli agent adapter, read first, prerequisites, entry points and utf-8 / unicode safeguards.
fanqie-publisher-skill CLAUDE.md
Instructions for amm10090/fanqie-publisher-skill, covering fanqie-publisher-skill — claude code adapter, read first, entry points, prerequisites and utf-8 / unicode safeguards.