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/lena-ee/simple_mcp/claude-mdgit clone --depth 1 https://github.com/LENA-EE/simple_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/lena-ee/simple_mcp/claude-md)<a href="https://agentmods.dev/instructions/lena-ee/simple_mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/lena-ee/simple_mcp/claude-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.02806 | $0.02806 |
| Opus 5 | $0.01403 | $0.01403 |
| Sonnet 5 | $0.00561 | $0.00561 |
| Haiku 4.5 | $0.00281 | $0.00281 |
Grade A, and why
simple_mcp CLAUDE.md scanned grade A 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- `/deploy` — финальная проверка обязательно включает: smoke test `test_server.py`, ручной `curl POST /sse` с `tools/list`, проверку, что `raw_output` не утекает в ответ. How it starts
The opening of the file, as written. The whole thing — 252 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — Исполнительный контракт агента
Стандарт: AI Engineering Standard (AES) v1.2
Compliance Level: AES-L2 (конституция + approved spec.md + plan.md в specs/)
Цель в зрелости: AES-L3 (CLAUDE.md настроен, 0 AES violations в последнем PR)
Этот файл — нормативный контракт между Human Architect и AI-агентом для репозитория
mcp-drospr. Базовые правила наследуются из AES v1.2 (CLAUDE.mdстандарта) — см. ссылку выше. Здесь зафиксированы проектно-специфичные дополнения и обязательные нотификации, которые ловят реальные ошибки в этом проекте.При конфликте:
PROJECT_CONSTITUTION.md> этот файл > AES v1.2 baseline > предположения агента.
0. Required Inputs
Перед любой реализацией агент MUST прочитать:
PROJECT_CONSTITUTION.md— продуктовый и архитектурный авторитет проекта.- Этот файл целиком.
- Релевантные документы из
docs/иspecs/под текущую задачу.
Если конституция отсутствует или противоречит запросу — агент MUST STOP и попросить разъяснение.
1. Roles & Authority
Наследуется из AES v1.2 §1 без изменений.
The Agent executes decisions — it does not originate them.
В контексте mcp-drospr:
- Human Architect владеет продуктовыми и архитектурными решениями (см. roadmap в
PROJECT_CONSTITUTION.md). - Агент работает как senior software engineer, исполняющий согласованные шаги.
- Феникс/Qwen не является агентом-исполнителем этого контракта — Феникс получает от MCP только данные и отвечает разработчику. Контракт распространяется на coding-агентов в IDE (Claude Code, Kilo, opencode и т. п.).
2. Agent State Model
Наследуется из AES v1.2 §3 без изменений:
DISCOVERY → PLANNING → EXECUTION → REVIEW → DEPLOYMENT
Переходы между состояниями требуют артефактов — см. AES v1.2 §4.
Для нетривиальной фичи spec.md и plan.md хранятся в specs/<NNN>-<slug>/ (см. существующие 001-analyze-perl-diff, 002-check-before-push).
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 · 252 lines · 2,806 tokens per session scan A 5bb87e9f7858
simple_mcp CLAUDE.md is an instructions file published in the GitHub repository LENA-EE/simple_mcp (0 stars, last pushed 3mo ago), licensed MIT. It adds 2,806 tokens to every session, about $0.0140 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
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.
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).
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.
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).