Borrowing it
Nothing to install: this file belongs to kratsg/ami-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.
curl -O https://raw.githubusercontent.com/kratsg/ami-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/kratsg/ami-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/kratsg/ami-mcp/claude-md)<a href="https://agentmods.dev/instructions/kratsg/ami-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/kratsg/ami-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.03405 | $0.03405 |
| Opus 5 | $0.01702 | $0.01702 |
| Sonnet 5 | $0.00681 | $0.00681 |
| Haiku 4.5 | $0.00341 | $0.00341 |
Grade A, and why
ami-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 6d 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 — 357 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ami-mcp — Contributor Guide
MCP server that wraps ATLAS AMI (ATLAS Metadata Interface) and the PMG cross-section database, exposing them as tools for LLMs.
Architecture
LLM <--MCP/stdio--> ami-mcp serve <--HTTPS (pyAMI)--> AMI server (atlas-ami.cern.ch)
|
+--filesystem--> PMGxsecDB*.txt (cross-section DB on CVMFS)
Design philosophy: MCP resources document the AMI query DSL. The LLM reads
those resources, formulates AMI command strings itself, then calls tools like
ami_execute with those strings. We do NOT hide query construction behind
hundreds of wrappers — instead we give the LLM the DSL and let it be expressive.
Project layout
src/ami_mcp/
├── __init__.py # version
├── _version.pyi # type stub
├── py.typed
├── cli.py # argparse: `ami-mcp serve`
├── server.py # FastMCP setup, lifespan (pyAMI client init), tool registration
├── nomenclature.py # ATLAS naming + hashtag + campaign constants (used by resources.py)
├── resources.py # MCP resources: AMI query language ref, nomenclature, commands
└── tools/
├── __init__.py
├── _helpers.py # format_ami_result(), run_ami_command(), scope_to_catalog()
├── execute.py # ami_execute (general purpose AMI command execution)
├── datasets.py # ami_get_dataset_info, ami_list_datasets, ami_get_dataset_prov
├── hashtags.py # ami_search_by_hashtags, ami_get_dataset_hashtags
├── physics.py # ami_get_physics_params
├── tags.py # ami_get_ami_tag
├── xsecdb.py # ami_list_xsec_databases, ami_lookup_xsec
└── validate.py # ami_validate_sample
tests/
├── conftest.py # mock_ami_client, mock_ctx fixtures
├── test_package.py
├── test_cli.py
├── test_server.py
├── test_resources.py
├── test_tools_execute.py
├── test_tools_datasets.py
├── test_tools_hashtags.py
├── test_tools_physics.py
├── test_tools_tags.py
├── test_tools_xsecdb.py
└── integration/test_live.py # requires live AMI access, run with --runslow
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.
- 6d ago First seen · 357 lines · 3,405 tokens per session scan A a0c93424fcfe
ami-mcp CLAUDE.md is an instructions file published in the GitHub repository kratsg/ami-mcp (2 stars, last pushed 9d ago), licensed Apache-2.0. It adds 3,405 tokens to every session, about $0.0170 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.