Borrowing it
Nothing to install: this file belongs to ciinkwia/lithium-vault-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/ciinkwia/lithium-vault-mcp/master/CLAUDE.mdgit clone --depth 1 https://github.com/ciinkwia/lithium-vault-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/ciinkwia/lithium-vault-mcp/claude-md)<a href="https://agentmods.dev/instructions/ciinkwia/lithium-vault-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/ciinkwia/lithium-vault-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/ciinkwia/lithium-vault-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/ciinkwia/lithium-vault-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.01997 | $0.01997 |
| Opus 5 | $0.00999 | $0.00999 |
| Sonnet 5 | $0.00399 | $0.00399 |
| Haiku 4.5 | $0.00200 | $0.00200 |
Grade A, and why
lithium-vault-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 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
lithium-vault-mcp
MCP server that exposes the Lithium Research Vault's three paid x402 tiers as MCP tools, so Claude Desktop / Claude Code users can query primary-source lithium mining data from inside their agent. Model A (bring-your-own-wallet): the server pays the vault's x402 fee from the caller's CDP wallet.
Lithium tie-in: this is the MCP distribution channel for the lithium-research
vault (see ../clink-wallet/services/vault/). Part of the vault's go-to-market
(../clink-wallet/services/vault/GO_TO_MARKET.md, item #6).
Scaffolded + PUBLISHED 2026-05-31.
- npm:
[email protected](npx -y lithium-vault-mcpverified). Published by npm userbaldwijw(ciinkwia's npm account, no 2FA) via a temporary granular bypass-2FA token — npm rejects a plain token with 403 even on no-2FA accounts. For republishes:npm loginor a new bypass-2FA + read/write-all-packages granular token, thennpm publish --access public. - GitHub: ciinkwia/lithium-vault-mcp (public).
- End-to-end tested against Base mainnet (MCP→x402→vault→data) + price-guard verified.
Why Model A (and the seam to Model C)
Two models were weighed (see GO_TO_MARKET.md):
- A — BYOW x402: caller pays from their own wallet; paywall intact; reaches only x402-equipped users. Chosen as a cheap experiment with bounded downside.
- C — hosted freemium: free summary tier served direct from DuckDB, paid depth via x402; huge reach. The fallback if A stalls on adoption.
Decision (2026-05-31): ship A; switch to C if adoption stalls. A's likely failure mode (wallet friction) is itself the evidence that would justify C.
The code is structured so A→C is additive, not a rewrite:
src/tools.js— tool catalog (names, zod schemas, descriptions,tier). Transport- and payment-agnostic. Reused verbatim by C.src/datasource.js—DataSourcecontract (fetchTier(tier, {entity, level})). A shipsX402DataSource(pays the endpoint from the caller's wallet, with a pre-flight price-ceiling check). C adds aDirectDataSource(reads the vault DuckDB free + upsell) implementing the same contract.src/x402.js— builds the x402-wrapped fetch bound to the caller's CDP wallet.src/index.js— wires the MCP stdio transport + the chosen data source. C swaps stdio→HTTP and the data source here; tools.js untouched.
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 · 123 lines · 1,997 tokens per session scan A 508062db903f
lithium-vault-mcp CLAUDE.md is an instructions file published in the GitHub repository ciinkwia/lithium-vault-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 1,997 tokens to every session, about $0.0100 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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.