Borrowing it
Nothing to install: this file belongs to CedricConday/xe-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/CedricConday/xe-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/CedricConday/xe-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/cedricconday/xe-mcp/claude-md)<a href="https://agentmods.dev/instructions/cedricconday/xe-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/cedricconday/xe-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.00672 | $0.00672 |
| Opus 5 | $0.00336 | $0.00336 |
| Sonnet 5 | $0.00134 | $0.00134 |
| Haiku 4.5 | $0.00067 | $0.00067 |
Grade A, and why
xe-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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
xe-mcp — Claude Code Instructions
What this project is
An MCP server for the Xe Currency Data API. Eleven tools spanning rate lookup, conversion, historical analysis, volatility, moving averages, correlation, alert checking, and charting. Falls back to Frankfurter (ECB) when Xe credentials aren't set.
Build and test
npm install # install deps
npm run build # compile TypeScript → dist/ (MCP server)
npm run build:lambda # compile → dist-lambda/ (Lambda handlers)
npm run build:all # compile both
npm test # run Jest unit tests (49 tests, 5 suites)
bash scripts/smoke-test.sh # 12/12 live tool smoke test (requires npm run build first)
Build must pass before any commit. Tests must pass before any PR.
Architecture
src/
├── index.ts # MCP server entry — 12 tools, stdio transport
├── xe-client.ts # Xe XECD API wrapper (auth: HTTP Basic)
├── frankfurter-client.ts # ECB fallback (free, no auth)
├── s3-cache.ts # S3-backed rate history cache (Lambda use)
└── tools/
├── rates.ts # get_rate, convert, list_currencies
├── analysis.ts # get_historical_rates, volatility_analysis, optimal_send_window, moving_average
├── nzd.ts # nzd_corridors
├── correlation.ts # correlation_analysis
├── alerts.ts # rate_alert_check
└── chart.ts # rate_chart
lambda/
├── handler.ts # REST API — all 12 tools via POST /tool/{name}
├── alert-scheduler.ts # CloudWatch hourly → DynamoDB → SQS
└── alert-processor.ts # SQS consumer → SES email
Adding a new tool
- Create
src/tools/your-tool.tswith a tool definition object and handler function - Import and register both in
src/index.ts(tools list + switch case) - Also register in
lambda/handler.tsswitch statement - Write tests in
src/__tests__/your-tool.test.tscovering the math or logic - Add the tool to
scripts/smoke-test.sh - Rebuild and run tests before committing
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 · 67 lines · 672 tokens per session scan A 953f067e06a2
xe-mcp CLAUDE.md is an instructions file published in the GitHub repository CedricConday/xe-mcp (1 stars, last pushed 2mo ago), licensed MIT. It adds 672 tokens to every session, about $0.0034 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
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).
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.
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).
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.