Borrowing it
Nothing to install: this file belongs to Joint-Photon-Sciences-Institute/xraylarch-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/Joint-Photon-Sciences-Institute/xraylarch-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/Joint-Photon-Sciences-Institute/xraylarch-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/joint-photon-sciences-institute/xraylarch-mcp/claude-md)<a href="https://agentmods.dev/instructions/joint-photon-sciences-institute/xraylarch-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/joint-photon-sciences-institute/xraylarch-mcp/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/joint-photon-sciences-institute/xraylarch-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/joint-photon-sciences-institute/xraylarch-mcp/claude-md.svg" alt="Reviewed on agentmods" width="80" 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.04335 | $0.04335 |
| Opus 5 | $0.02167 | $0.02167 |
| Sonnet 5 | $0.00867 | $0.00867 |
| Haiku 4.5 | $0.00434 | $0.00434 |
Grade A, and why
xraylarch-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 12d 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 — 468 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — xraylarch-mcp Builder
Mission
Build a production-quality MCP (Model Context Protocol) server that wraps xraylarch (the headless X-ray spectroscopy analysis library) so that Claude can load, process, analyze, and plot X-ray spectra through natural tool calls. The package should be pip-installable and usable via Claude Desktop or Claude Code with zero configuration beyond pip install.
Repository
git remote: https://github.com/Joint-Photon-Sciences-Institute/xraylarch-mcp.git
branch: main
Phase 0: Probe xraylarch (DO THIS FIRST)
Before writing any MCP code, you must understand the xraylarch API by introspecting it directly. Do NOT rely on your training data — larch's API evolves and your knowledge may be stale.
0.1 Install xraylarch (headless)
pip install xraylarch
# Do NOT install GUI dependencies — we only need the computational core
0.2 Discover the API surface
Run Python introspection to catalog functions, their signatures, and docstrings. Focus on these critical modules:
import larch
from larch import Interpreter
session = Interpreter()
# Core I/O — discover all readers
import larch.io
# List all public functions: dir(larch.io)
# For each reader (read_ascii, read_xdi, read_athena, read_gsexdi, etc.):
# - inspect.signature(func)
# - func.__doc__
# XAFS analysis — the most important module
from larch.xafs import (
pre_edge, autobk, xftf, xftr, xftf_fast,
feffit, feffit_dataset, feffit_transform, feffpath,
fluo_corr, over_absorption, mback, mback_norm,
estimate_noise, pre_edge_baseline
)
# For each: get signature, docstring, required/optional params, defaults
# XRF analysis
from larch.xrf import xrf_background, xrf_calib_energy, xrf_calib_compute
# Fitting
from larch.fitting import param, param_group, guess, minimize, confidence_intervals
# XES (X-ray emission spectroscopy)
# Check if larch.xes exists, catalog it
# Math/utilities
from larch.math import (
index_of, index_nearest, interp, smooth, deriv,
pca_train, pca_fit, nmf_train
)
# FEFF interface
from larch.xafs import feffpath, feffit, feffit_dataset, feffit_transform
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.
- 12d ago First seen · 468 lines · 4,335 tokens per session scan A 8d04141b05ec
xraylarch-mcp CLAUDE.md is an instructions file published in the GitHub repository Joint-Photon-Sciences-Institute/xraylarch-mcp (2 stars, last pushed 6mo ago), licensed BSD-3-Clause. It adds 4,335 tokens to every session, about $0.0217 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
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.
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).
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).