Borrowing it
Nothing to install: this file belongs to Johnaverse/chains-api. 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/Johnaverse/chains-api/main/CLAUDE.mdgit clone --depth 1 https://github.com/Johnaverse/chains-apiWrote 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/johnaverse/chains-api/claude-md)<a href="https://agentmods.dev/instructions/johnaverse/chains-api/claude-md"><img src="https://agentmods.dev/badge/instructions/johnaverse/chains-api/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/johnaverse/chains-api/claude-md"><img src="https://agentmods.dev/badge/instructions/johnaverse/chains-api/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.06812 | $0.06812 |
| Opus 5.5 | $0.02725 | $0.02725 |
| Sonnet 5.5 | $0.01362 | $0.01362 |
| Haiku 4.5 | $0.00681 | $0.00681 |
Grade A, and why
chains-api 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 today.
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 — 277 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — Chains API
Project Overview
Chains API is a Node.js service that aggregates blockchain chain data from five external sources, maintains an in-memory index, and exposes it via a REST API (Fastify), MCP stdio server, and MCP HTTP server. No database — data is fetched from remote JSON/Markdown sources, indexed in memory, and optionally cached to disk for stale-first startup.
Single data source per container: server.js runs the REST API and the MCP HTTP server in one process (default npm start / Docker CMD). Both surfaces read the same module-level in-memory store (src/store/), and only the REST side starts the refreshers — so a container never refreshes the same public RPC endpoint twice. index.js (REST only) and mcp-server-http.js (MCP only) remain runnable standalone for local/dev use. The MCP tool surface in mcp-tools.js mirrors the REST read endpoints (chains, search, relations, endpoints, clients, scaling, slip44, status-pages, stats, keywords, rpc-monitor, refresher, validate, live-incidents, forum-news).
Upstream feed services (separate deployables): live incidents, forum news and ecosystem news do not come from the five data sources — they are served by three sibling Node services with their own repos, releases, and containers:
| Service | Feeds | Consumed via |
|---|---|---|
chains-status-news |
Chain + RPC-provider status pages → incidents, scheduled maintenance | LIVE_INCIDENTS_URL |
chains-forum-news |
Official community/governance forums, keyed by chain ID | FORUM_NEWS_URL |
chains-news |
Curated ecosystem publishers (project blogs = primary, news desks = secondary) |
WEB3_NEWS_URL |
chains-client-feed |
Blockchain client releases/changelogs → hard-fork activations; client → networks index built from GET /repositories (research + hardware links + the curated data/client-registry-overrides.json, and client lineage families/links from data/client-lineage.json; the feed bundles no registry of its own) |
CLIENT_FEED_URL (optional): /forks, /client-releases* proxy (dashboard Releases view + chain-drawer Clients), get_client_releases (with since/until) / get_latest_release (/client-releases/latest: one repo's latest version + link, hard fork, mandatory, security — advisory or notes —, flag/config changes; null = unknown) / get_network_clients / get_client_activity (with lineage) |
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.
- today Changed · +1 lines · +40 tokens per session 0d218bd3d46f
- 4d ago Changed · +2 lines · +82 tokens per session 41dbe7ae4054
- 6d ago Changed 8a9262f27e04
- 8d ago Changed · +43 tokens per session f146b1d3f449
- 9d ago Changed · +6 lines · +448 tokens per session dbb6d00a4258
- 10d ago Changed · +20 tokens per session b6db3dcc79a0
- 11d ago Changed · +4 lines · +332 tokens per session 219fe9641dd1
- 13d ago Changed · +175 tokens per session eb0f8f6326de
- 15d ago Changed · +1 lines · +213 tokens per session b56833f8b070
- 16d ago First seen · 263 lines · 5,459 tokens per session scan A 2d226ee6c108
chains-api CLAUDE.md is an instructions file published in the GitHub repository Johnaverse/chains-api (6 stars, last pushed today), licensed MIT. It adds 6,812 tokens to every session, about $0.0272 per session on Opus 5.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
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.