Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/refined-element/lightning-enable-mcp/claude-mdgit clone --depth 1 https://github.com/refined-element/lightning-enable-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/refined-element/lightning-enable-mcp/claude-md)<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="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.00514 | $0.00514 |
| Opus 5 | $0.00257 | $0.00257 |
| Sonnet 5 | $0.00103 | $0.00103 |
| Haiku 4.5 | $0.00051 | $0.00051 |
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 5d 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 — 32 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 THREE files in the SAME commit, then push to main:
dotnet/src/LightningEnable.Mcp/LightningEnable.Mcp.csproj—<Version>python/lightning-enable-mcp/pyproject.toml—versionserver.json—.version, both.packages[].version(nuget + pypi), and the Docker image pin in.packages[2].identifier(docker.io/refinedelement/lightning-enable-mcp:<version>)
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).
Bug Fix Workflow
When a bug is reported, do NOT immediately start trying to fix it. Follow this process:
- Write a failing test first — Reproduce the bug with a test that proves it fails
- Fix the bug — Use subagents to implement the fix
- Prove the fix — Show the test now passes
Engineering Standards
Inherited from Lightning Enable — these apply to all ecosystem properties.
- User-facing error messages: Never return blank/empty responses on failure. Always provide descriptive error context.
- Graceful error handling: Handle all errors gracefully. Never let unhandled exceptions crash the process or leak stack traces.
- Never log sensitive data: Never log API keys, wallet credentials, macaroons, preimages, or NWC connection strings. Use safe identifiers only.
- Secret key exposure: If any credentials are potentially leaked (in logs, responses, git history), flag to the user IMMEDIATELY.
- Enterprise scale: Flag any patterns that won't scale to hundreds of thousands of concurrent users.
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.
- 5d ago First seen · 32 lines · 514 tokens per session scan A 4aff0160566e
lightning-enable-mcp CLAUDE.md is an instructions file published in the GitHub repository refined-element/lightning-enable-mcp (9 stars, last pushed 2d ago), licensed MIT. It adds 514 tokens to every session, about $0.0026 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
SaturnZap copilot-instructions.md
Instructions for lqwdtech/SaturnZap, covering saturnzap — copilot instructions, build & test, architecture, conventions and test patterns.
SaturnZap tests.instructions.md
Use when writing, editing, or debugging SaturnZap tests. Covers fixtures, mocking patterns, CLI runner usage, and live test markers.
polar CLAUDE.md
Claude Code instructions for jamaljsr/polar, covering claude.md, about polar, essential commands, development and testing individual files.
polar copilot-instructions.md
Copilot instructions for jamaljsr/polar, covering polar - ai coding assistant instructions, core architecture, network orchestration via docker compose, state management (easy-peasy + redux) and visual designer (react flow chart).
sparkbtcbot CLAUDE.md
Claude Code instructions for echennells/sparkbtcbot, covering sparkbtcbot, what this skill does, structure, trigger phrases and dependencies.
agentic-aqua AGENTS.md
Instructions for jan3dev/agentic-aqua, covering agentic-aqua, architecture, layout, entry points and dev commands.