anchorage-ecode-mcp: Instructions file for Claude Code

CLAUDE.md

anchorage-ecode-mcp CLAUDE.md is an instructions file for Claude Code from codeforanchorage/anchorage-ecode-mcp. It costs 1,306 tokens per session, scanned A, original, MIT.

A repository instruction file for codeforanchorage/anchorage-ecode-mcp. It documents development commands, local server startup, configuration validation, tests, and linting.

In plain words
What is it for?
Use it to install dependencies, run the local MCP server, validate configuration, run tests, and check Python code style.
Why use it?
It tells an agent how this project is structured and how to check changes using the same validation steps as the project.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions CLAUDE.md; mentions Claude Code.

This is codeforanchorage/anchorage-ecode-mcp's own configuration. It tells Claude Code how to work on anchorage-ecode-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything anchorage-ecode-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to codeforanchorage/anchorage-ecode-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/codeforanchorage/anchorage-ecode-mcp/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/codeforanchorage/anchorage-ecode-mcp

Made for: Claude Code.

Wrote 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.

agentmods badge for anchorage-ecode-mcp CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/codeforanchorage/anchorage-ecode-mcp/claude-md.svg)](https://agentmods.dev/instructions/codeforanchorage/anchorage-ecode-mcp/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/codeforanchorage/anchorage-ecode-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/codeforanchorage/anchorage-ecode-mcp/claude-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 1,306 This file is loaded in full into every session.
When invoked 1,306 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.01306 $0.01306
Opus 5 $0.00653 $0.00653
Sonnet 5 $0.00261 $0.00261
Haiku 4.5 $0.00131 $0.00131

Measured 7d ago against content hash f15626b61012, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

anchorage-ecode-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 7d 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.

CLAUDE.md · 89 lines

How it starts

The opening of the file, as written. The whole thing — 89 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.

Build & Development Commands

# Install dependencies (uv preferred, pip fallback)
uv sync                              # or: pip install -r requirements.txt

# Run local MCP server (no Lambda needed)
python3 scripts/local_server.py      # Serves on http://localhost:8000/mcp
# Single entry point. It routes through UniversalHTTPHandler, so local dev
# enforces the same Origin allowlist, MCP-Protocol-Version check and
# path/method validation as prod.

# Validate config
python3 -c "from core.validators import load_and_validate_config; load_and_validate_config('config.yaml')"

# Tests
uv run pytest tests/ -n auto                                    # All tests, parallel
uv run pytest tests/test_ckan_plugin.py -v                      # Single file
uv run pytest tests/test_ckan_plugin.py::TestClass::test_name -v  # Single test
uv run pytest tests/ --cov=core --cov=plugins --cov-report=term-missing  # With coverage (80% minimum)

# Linting (ruff)
uv run ruff check core/ plugins/ server/ tests/      # Check
uv run ruff check core/ plugins/ server/ tests/ --fix # Auto-fix
uv run ruff format core/ plugins/ server/ tests/      # Format

# Pre-commit hooks
pre-commit run --all-files

# Go client (requires Go 1.21+)
cd client && make build

# Deploy to AWS
./scripts/deploy.sh --environment staging

Architecture

Core rule: One Fork = One MCP Server. Each deployment runs exactly ONE plugin. This is enforced at config validation time (core/validators.py) and at runtime (PluginManager.load_plugins()). To deploy multiple MCP servers, fork the repo per plugin.

Request flow:

Claude (stdio) → Go client (client/) or stdio_bridge.py → HTTP POST /mcp
  → Lambda (server/adapters/aws_lambda.py) or scripts/local_server.py
  → server/http_handler.py → core/mcp_server.py (JSON-RPC 2.0)
  → core/plugin_manager.py → Plugin → External API

Key modules:

  • core/interfaces.py — Abstract bases: MCPPlugin, DataPlugin, plus ToolDefinition, ToolResult, PluginType enum
  • core/plugin_manager.py — Discovers plugins by scanning plugins/ and custom_plugins/ for plugin.py files. Registers tools with pluginname__toolname prefix. Routes tools/call to the correct plugin.
  • core/mcp_server.py — Handles MCP JSON-RPC methods: initialize, tools/list, tools/call, ping
  • core/validators.py — Loads config from config.yaml (local) or OPENCONTEXT_CONFIG env var (Lambda). Enforces single-plugin rule.
  • server/adapters/aws_lambda.py — the ONLY AWS Lambda entry point (handler: server.adapters.aws_lambda.lambda_handler), and the only thing Terraform points at.
  • server/http_handler.py — Cloud-agnostic HTTP handler shared by Lambda and local server
  • stdio_bridge.py — Python stdio-to-HTTP bridge for connecting Claude Desktop/Code to the local server (alternative to Go client)

Read the full file on GitHub · 89 lines

Changes

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.

  1. 7d ago First seen · 89 lines · 1,306 tokens per session scan A f15626b61012

Subscribe to this mod's changes

anchorage-ecode-mcp CLAUDE.md is an instructions file published in the GitHub repository codeforanchorage/anchorage-ecode-mcp (0 stars, last pushed 12d ago), licensed MIT. It adds 1,306 tokens to every session, about $0.0065 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.

Related

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.

vercel/next.js · 7,296 tokens

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.

openai/codex · 5,153 tokens

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).

microsoft/vscode · 6,785 tokens

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).

microsoft/vscode · 5,001 tokens

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.

langchain-ai/langchain · 4,469 tokens

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.

github/spec-kit · 7,104 tokens