lightning-enable-mcp: Instructions file for Claude Code

CLAUDE.md

lightning-enable-mcp CLAUDE.md is an instructions file for Claude Code from refined-element/lightning-enable-mcp. It costs 1,301 tokens per session, scanned A, original, MIT.

A developer guide for Lightning Enable’s MCP server, which lets AI agents make payments over the Lightning Network, a system for fast Bitcoin payments. It describes the project and the checks required before publishing a new version.

In plain words
What is it for?
Use it when fixing bugs, updating release versions, checking the .NET, Python, Docker, or registry packages, or preparing a release.
Why use it?
It prevents release files from showing different versions and helps catch registry or package metadata errors before publication.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions CLAUDE.md; mentions subagents.

This is refined-element/lightning-enable-mcp's own configuration. It tells Claude Code how to work on lightning-enable-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything lightning-enable-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to refined-element/lightning-enable-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.

Copy the file
curl -O https://raw.githubusercontent.com/refined-element/lightning-enable-mcp/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/refined-element/lightning-enable-mcp

Made for: Claude Code.

Wrote 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.

agentmods badge for lightning-enable-mcp CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/refined-element/lightning-enable-mcp/claude-md/github.svg)](https://agentmods.dev/instructions/refined-element/lightning-enable-mcp/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/refined-element/lightning-enable-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/refined-element/lightning-enable-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.

agentmods 80×15 button for lightning-enable-mcp CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/refined-element/lightning-enable-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/refined-element/lightning-enable-mcp/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,301 This file is loaded in full into every session.
When invoked 1,301 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.01301 $0.01301
Opus 5.5 $0.00520 $0.00520
Sonnet 5.5 $0.00260 $0.00260
Haiku 4.5 $0.00130 $0.00130

Measured 22d ago against content hash 7ebc873375f7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

lightning-enable-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 22d 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.

CLAUDE.md · 78 lines

How it starts

The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CLAUDE.md — Lightning Enable MCP

Project Overview

Part of Lightning Enable — infrastructure for agent commerce over Lightning.

Open-source (MIT) MCP server for AI agent Lightning payments. See the main repo at F:\lightning-enable for full context.

Publishing: Bump the version in ALL SIX files in the SAME commit, then push to main:

  1. dotnet/src/LightningEnable.Mcp/LightningEnable.Mcp.csproj — <Version>
  2. python/lightning-enable-mcp/pyproject.toml — version
  3. server.json — .version, both .packages[].version (nuget + pypi), and the Docker image pin in .packages[2].identifier (docker.io/refinedelement/lightning-enable-mcp:<version>)
  4. mcpb/manifest.json — .version
  5. mcpb/pyproject.toml — version and the lightning-enable-mcp==<version> dependency pin
  6. dotnet/src/LightningEnable.Mcp/Services/UserAgent.cs — FallbackVersion (the last-resort User-Agent version, used only if the assembly has no version). UserAgentTests fails the .NET suite on drift; publish-mcp.yml does not check it.

publish-mcp.yml's verify-versions job checks the first five and fails the whole publish on any drift (2.0.3 was caught this way).

server.json is committed source-of-truth for the MCP Registry entry — it is NOT rewritten at publish time. publish-mcp.yml verifies it matches the release version and fails the registry publish on any drift, so a partial bump (e.g. csproj/pyproject bumped but server.json left stale) is caught before it strands registry.modelcontextprotocol.io on an old version. server.json's description must be ≤100 chars (also enforced by MCP Registry and CI validation).

Approval channel (out-of-band confirmation)

Over-threshold payments require a human-relayed confirmation code. The code is the operator's, never the model's — it must never appear in a tool result on any channel, and a payment is never approved because its notification could not be delivered (a delivery failure REFUSES the payment and withdraws the minted code).

Read the full file on GitHub · 78 lines

Changes

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.

  1. 22d ago Changed · +1 lines · +65 tokens per session 7ebc873375f7
  2. 1mo ago Changed · +8 lines · +137 tokens per session 8cf6cadf5fca
  3. 1mo ago Changed · +4 lines · +81 tokens per session 26ab7819abdd
  4. 1mo ago Changed · +33 lines · +504 tokens per session a0ccfb31f519
  5. 2mo ago First seen · 32 lines · 514 tokens per session scan A 4aff0160566e

Subscribe to this mod's changes

lightning-enable-mcp CLAUDE.md is an instructions file published in the GitHub repository refined-element/lightning-enable-mcp (9 stars, last pushed 11d ago), licensed MIT. It adds 1,301 tokens to every session, about $0.0052 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.

Related

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).

microsoft/vscode · 9,719 tokens

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.

vercel/next.js · 7,461 tokens

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).

microsoft/vscode · 5,334 tokens

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.

langchain-ai/langchain · 4,680 tokens

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).

microsoft/vscode · 2,792 tokens

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.

deepseek-ai/deepseek-harness · 4,261 tokens