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/koki-develop/esa-mcp-server/claude-mdgit clone --depth 1 https://github.com/koki-develop/esa-mcp-serverWrote 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/koki-develop/esa-mcp-server/claude-md)<a href="https://agentmods.dev/instructions/koki-develop/esa-mcp-server/claude-md"><img src="https://agentmods.dev/badge/instructions/koki-develop/esa-mcp-server/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.00705 | $0.00705 |
| Opus 5 | $0.00352 | $0.00352 |
| Sonnet 5 | $0.00141 | $0.00141 |
| Haiku 4.5 | $0.00071 | $0.00071 |
Grade A, and why
esa-mcp-server 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 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.
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 — 90 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
This is an MCP (Model Context Protocol) server for esa.io (information sharing service). It enables MCP clients (like Claude Desktop or Cody) to interact with esa.io's API.
Development Commands
Build, Type Check, and Lint
# Build the project (outputs to dist/)
bun run build
# TypeScript type checking
bun run typecheck
# Check code with Biome
bun run lint
# Auto-fix code with Biome
bun run fmt
Testing
# Run MCP Inspector for manual testing
bun run inspector
Dependency Management
# Install dependencies
bun install
# Add dependencies
bun add <package-name>
bun add -D <package-name> # Development dependencies
Architecture
Directory Structure
src/index.ts- Entry point (runs MCP protocol via stdio)src/server.ts- MCP server implementation (server name, tool registration)src/mcp/tools/- MCP tool definitions (implement each tool here)src/lib/esa/- esa.io API client implementationindex.ts- Esa class (API client)types.ts- Zod schemas and type definitions
scripts/build.ts- Bun build script (generates executable)
Build System
- Uses Bun's native build capabilities to generate a single executable
- Build configuration managed in
scripts/build.ts - Dockerfile uses multi-stage build
How to Implement MCP Tools
- Create new tool in
src/mcp/tools/ - Define input using zod schema
- Register tool in
src/mcp/tools/index.ts - Add to tools object in
src/server.ts
Current Implementation Status
- Basic MCP server structure implemented
- esa.io API client (
Esaclass) with Bearer auth - Environment variables:
ESA_TEAM,ESA_ACCESS_TOKEN
Implemented Tools
get_posts- fetches posts with filtering, sorting, paginationget_post- fetches specific post by numbercreate_post- creates new postupdate_post- updates existing postdelete_post- deletes postget_tags- fetches all tagsget_post_comments- fetches comments for a postcreate_post_comment- creates comment on post (write operation)update_comment- updates existing commentdelete_comment- deletes comment
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 · 90 lines · 705 tokens per session scan A 0c61b739b714
esa-mcp-server CLAUDE.md is an instructions file published in the GitHub repository koki-develop/esa-mcp-server (2 stars, last pushed 11mo ago), licensed MIT. It adds 705 tokens to every session, about $0.0035 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-31.
Other instructions, from other repositories
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.