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/segentic-lab/codelens-mcp/agents-mdgit clone --depth 1 https://github.com/segentic-lab/codelens-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/segentic-lab/codelens-mcp/agents-md)<a href="https://agentmods.dev/instructions/segentic-lab/codelens-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/segentic-lab/codelens-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 | $0.01281 | $0.01281 |
| Opus 5 | $0.00641 | $0.00641 |
| Sonnet 5 | $0.00256 | $0.00256 |
| Haiku 4.5 | $0.00128 | $0.00128 |
Grade C, and why
codelens-mcp AGENTS.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 4d 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.
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.
<!-- Copy everything below this line into your agent's system prompt to teach it how to use the codelens MCP tools effectively. --> The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 4d ago First seen · 89 lines · 1,281 tokens per session scan C 0a86caf785d7
codelens-mcp AGENTS.md is an instructions file published in the GitHub repository segentic-lab/codelens-mcp (1 stars, last pushed 2mo ago), licensed AGPL-3.0. It adds 1,281 tokens to every session, about $0.0064 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
tiger-cli CLAUDE.md
Instructions for timescale/tiger-cli, covering claude.md, naming guidelines, official names, examples and development commands.
mcp-server copilot-instructions.md
Instructions for ALCops/mcp-server, covering copilot instructions, build, build (requires bc devtools dlls, see below), run tests and pack as .net global tool.
sonde AGENTS.md
AGENTS.md instructions for anishmoncivarghese/sonde, covering project history, recording decisions, handing off active work, sonde and picking up this project (any agent, any vendor).
flyto-indexer AGENTS.md
AGENTS.md instructions for flytohub/flyto-indexer, covering agent rules, gate remediation loop, flyto2 project memory contract and flyto2 frontend quality gate.
flyto-indexer CLAUDE.md
Claude Code instructions for flytohub/flyto-indexer, covering claude notes, cross-agent handoff, shared code intelligence, code intelligence (flyto-indexer) and first-time setup.
booster_mcp AGENTS.md
AGENTS.md instructions for NeuroGhostDev/booster_mcp, covering booster agent bootstrap, bootstrap contract, engineering workflow, context priority and important boundary.