Borrowing it
Nothing to install: this file belongs to PaulMRamirez/yamcs-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/PaulMRamirez/yamcs-mcp-server/main/CLAUDE.mdgit clone --depth 1 https://github.com/PaulMRamirez/yamcs-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/paulmramirez/yamcs-mcp-server/claude-md)<a href="https://agentmods.dev/instructions/paulmramirez/yamcs-mcp-server/claude-md"><img src="https://agentmods.dev/badge/instructions/paulmramirez/yamcs-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.1 | $0.02054 | $0.02054 |
| Opus 5 | $0.01027 | $0.01027 |
| Sonnet 5 | $0.00411 | $0.00411 |
| Haiku 4.5 | $0.00205 | $0.00205 |
Grade A, and why
yamcs-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 8d 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 — 243 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 a Model Context Protocol (MCP) server for Yamcs (Yet Another Mission Control System). It provides a bridge between AI assistants and mission control systems using FastMCP 2.x with a modular component architecture.
Key Commands
Development Setup
# Install all dependencies including dev tools
uv sync --all-extras
# Install pre-commit hooks
pre-commit install
Running the Server
# Run the server (will connect to Yamcs at http://localhost:8090)
uv run yamcs-mcp
# Run directly as Python module
uv run python -m yamcs_mcp.server
# Run in demo mode without Yamcs (shows warning but continues)
uv run python -m yamcs_mcp.server # Yamcs connection failure is non-fatal
Testing
# Run all tests with coverage
uv run pytest
# Run specific test file
uv run pytest tests/test_server.py -v
# Run specific test
uv run pytest tests/test_server.py::test_server_initialization -v
# Run tests with coverage report
uv run pytest --cov=yamcs_mcp --cov-report=html
Code Quality
# Run linting
uv run ruff check .
# Run linting with auto-fix
uv run ruff check . --fix
# Run type checking
uv run mypy src/
# Format code
uv run ruff format .
Architecture Overview
Server Composition Pattern
The server uses FastMCP's server composition pattern where each Yamcs subsystem is implemented as an independent FastMCP server that gets mounted to the main server:
-
BaseYamcsServer (
src/yamcs_mcp/servers/base_server.py)- Base class extending FastMCP for all servers
- Provides common functionality like error handling
- Each server is a full FastMCP instance
-
Servers (in
src/yamcs_mcp/servers/)- MDBServer - Mission Database operations
- LinksServer - Data link management
- ProcessorsServer - Processor control
- InstancesServer - Instance management
- StorageServer - Object storage operations
- AlarmsServer - Alarm management and monitoring
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.
- 8d ago First seen · 243 lines · 2,054 tokens per session scan A 5ea2f41e41e0
yamcs-mcp-server CLAUDE.md is an instructions file published in the GitHub repository PaulMRamirez/yamcs-mcp-server (4 stars, last pushed 10mo ago), licensed MIT. It adds 2,054 tokens to every session, about $0.0103 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
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).
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).
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.
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.