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/azmaveth/ex_mcp/claude-mdgit clone --depth 1 https://github.com/azmaveth/ex_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/azmaveth/ex_mcp/claude-md)<a href="https://agentmods.dev/instructions/azmaveth/ex_mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/azmaveth/ex_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.1 | $0.03053 | $0.03053 |
| Opus 5 | $0.01527 | $0.01527 |
| Sonnet 5 | $0.00611 | $0.00611 |
| Haiku 4.5 | $0.00305 | $0.00305 |
Grade A, and why
ex_mcp CLAUDE.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 5d 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 — 285 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Overview
ExMCP is an Elixir implementation of the Model Context Protocol (MCP), enabling AI models to communicate with external tools and resources through a standardized protocol.
Version Management
When to Bump Versions
- Patch version (0.x.Y): Bug fixes, documentation updates, minor improvements
- Minor version (0.X.0): New features, non-breaking API changes
- Major version (X.0.0): Breaking API changes (after 1.0.0 release)
Version Update Checklist
- Update version in
mix.exs - Update CHANGELOG.md with:
- Version number and date
- Added/Changed/Fixed/Removed sections
- BREAKING: prefix for any breaking changes
- Commit with message:
chore: bump version to X.Y.Z
CHANGELOG Format
## [X.Y.Z] - YYYY-MM-DD
### Added
- New features
### Changed
- Changes in existing functionality
- **BREAKING:** API changes that break compatibility
### Fixed
- Bug fixes
### Removed
- Removed features
- **BREAKING:** Removed APIs
Development Commands
# Essential commands
mix deps.get # Install dependencies
mix test # Run all tests
mix test test/ex_mcp/internal/protocol_compliance_test.exs # Run specific test file
mix format # Format code (required before committing)
mix credo # Static code analysis
mix dialyzer # Type checking (run after significant changes)
mix docs # Generate documentation
iex -S mix # Start interactive shell with project loaded
# Development workflow
mix compile --warnings-as-errors # Compile with strict warnings
MIX_ENV=test mix compile # Compile for test environment
mix sobelow --skip # Security analysis
mix coveralls.html # Generate coverage report
# Repo-only tooling (lives in dev/, never published to Hex)
mix test.suite <unit|compliance|integration|performance|all|ci>
mix test.tags # List the test tags and what they mean
mix test.cleanup # Kill stray processes/ports left by crashed tests
mix mcp.sync_spec # Sync upstream MCP spec docs into docs/mcp-specs/
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.
- 5d ago First seen · 285 lines · 3,053 tokens per session scan A 6c76c1678915
ex_mcp CLAUDE.md is an instructions file published in the GitHub repository azmaveth/ex_mcp (26 stars, last pushed today), licensed MIT. It adds 3,053 tokens to every session, about $0.0153 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
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.
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.
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).