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/lirantal/ls-mcp/agents-mdgit clone --depth 1 https://github.com/lirantal/ls-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/lirantal/ls-mcp/agents-md)<a href="https://agentmods.dev/instructions/lirantal/ls-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/lirantal/ls-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.00357 | $0.00357 |
| Opus 5 | $0.00179 | $0.00179 |
| Sonnet 5 | $0.00071 | $0.00071 |
| Haiku 4.5 | $0.00036 | $0.00036 |
Grade A, and why
ls-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 6d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- agent-rules AGENTS.md — 100% identical, 0 lines differ
- mcp-server-nodejs-api-docs AGENTS.md — 100% identical, 0 lines differ
What it actually says
AGENTS.md
Guidance for AI coding agents working in this repository.
Start Here
Before making changes, read:
CONTRIBUTING.mdfor contribution, PR, testing, commit, and agent-specific expectations.RELEASE.mdfor release workflow details.README.mdfor user-facing behavior, install/use examples, and package or app overview.docs/README.mdfor the project documentation index.docs/development.mdfor local setup and development workflows.docs/testing.mdfor test strategy, commands, and verification expectations.docs/architecture.mdfor project structure, boundaries, and important invariants.docs/conventions.mdfor project-specific coding, documentation, and maintenance conventions.
Treat those files as the source of truth. Do not duplicate or reinterpret their rules here.
Documentation
- Keep documentation in sync when changing behavior, public interfaces, workflows, architecture, configuration, or operational assumptions.
- Put project-specific development details in
docs/; keep root files focused on their standard audiences. - Prefer linking to the source of truth over duplicating long instructions across files.
- When adding new docs, link them from
docs/README.mdand update this file only when they become important entry points for future agents.
PRs and Issues
- Follow PR, issue, and agent-labeling rules in
CONTRIBUTING.md. - Use the issue-linking format specified in
CONTRIBUTING.md.
Releases
- Follow
RELEASE.mdfor release workflow and changeset creation steps. - If this project uses changesets, treat
RELEASE.mdand any changeset guidance inCONTRIBUTING.mdas authoritative.
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.
- 6d ago First seen · 36 lines · 357 tokens per session scan A ef27705e3cce
ls-mcp AGENTS.md is an instructions file published in the GitHub repository lirantal/ls-mcp (84 stars, last pushed 4d ago), licensed Apache-2.0. It adds 357 tokens to every session, about $0.0018 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
mcp-server-nodejs-api-docs AGENTS.md
AGENTS.md instructions for lirantal/mcp-server-nodejs-api-docs, covering agents.md, start here, documentation, prs and issues and releases.
cursor-handbook CLAUDE.md
Claude Code instructions for girijashankarj/cursor-handbook, covering claude.md — instructions for claude, project, critical rules, token efficiency (most important) and security (critical).
cursor-handbook AGENTS.md
AGENTS.md instructions for girijashankarj/cursor-handbook, covering agents.md — instructions for ai agents, project overview, key principles, 1. token efficiency and 2. security.
project-mem-mcp CLAUDE.md
Claude Code instructions for wallneradam/project-mem-mcp, covering claude.md, project overview, development commands, setup and run the server locally.
perplexity-web-api-mcp AGENTS.md
Instructions for mishamyrt/perplexity-web-api-mcp, covering agents.md — guidelines for ai agents, workspace & dependencies, async rust best practices (tokio), error handling & logging and code style & project hygiene.
mcp-image-extractor CLAUDE.md
Instructions for ifmelate/mcp-image-extractor, covering claude.md, project overview, commands, architecture and key constants & environment variables.