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.
curl -O https://raw.githubusercontent.com/refined-element/lightning-enable-mcp/main/.claude/skills/mcp-publish-prep/SKILL.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/skills/refined-element/lightning-enable-mcp/mcp-publish-prep)<a href="https://agentmods.dev/skills/refined-element/lightning-enable-mcp/mcp-publish-prep"><img src="https://agentmods.dev/badge/skills/refined-element/lightning-enable-mcp/mcp-publish-prep/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/skills/refined-element/lightning-enable-mcp/mcp-publish-prep"><img src="https://agentmods.dev/badge/skills/refined-element/lightning-enable-mcp/mcp-publish-prep.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.00021 | $0.00437 |
| Opus 5.5 | $0.00008 | $0.00175 |
| Sonnet 5.5 | $0.00004 | $0.00087 |
| Haiku 4.5 | $0.00002 | $0.00044 |
Grade A, and why
mcp-publish-prep 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.
What it actually says
Prepare the MCP package for a new release. Use $ARGUMENTS for the new version number (e.g., 1.5.0).
Steps
-
Bump version in BOTH files (CRITICAL — must be simultaneous):
dotnet/src/LightningEnable.Mcp/LightningEnable.Mcp.csproj— update<Version>python/lightning-enable-mcp/pyproject.toml— updateversiondotnet/src/LightningEnable.Mcp/Services/UserAgent.cs— updateFallbackVersion(UserAgentTestsfails on drift)- These MUST match. CI/CD publishes both from the same version.
-
Validate
server.json:- Check
descriptionfield is ≤100 characters (enforced by MCP Registry and CI) - Update
versionfield if present (CI auto-updates via jq, but good to keep in sync)
- Check
-
Update changelog if one exists
-
Build verification:
- Run
dotnet buildindotnet/src/LightningEnable.Mcp/ - Verify no build errors
- Run
-
Review CI/CD:
- Check
.github/workflows/publish-mcp.ymlis up to date - Verify secrets are configured:
NUGET_API_KEY,PYPI_API_TOKEN,DOCKERHUB_USERNAME,DOCKERHUB_TOKEN
- Check
Publishing targets (all automated on push to main):
- NuGet:
https://www.nuget.org/packages/LightningEnable.Mcp - PyPI:
https://pypi.org/project/lightning-enable-mcp - Docker Hub:
https://hub.docker.com/r/refinedelement/lightning-enable-mcp - MCP Registry:
https://registry.modelcontextprotocol.io
Output
Report the version bump, validation results, and build status. Remind the user to push to main to trigger CI/CD.
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.
- 22d ago Changed · +1 lines 486a58bc1ba1
- 2mo ago First seen · 37 lines · 21 tokens per session scan A abc9d601ebea
mcp-publish-prep is a skill published in the GitHub repository refined-element/lightning-enable-mcp (9 stars, last pushed 11d ago), licensed MIT. It adds 21 tokens to every session and 437 once invoked, about $0.0001 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 skills, from other repositories
saturnzap
Non-custodial Lightning wallet for AI agents via sz CLI: send/receive sats, pay invoices, auto-pay HTTP 402 (L402), manage channels and liquidity. Use when: (1) paying for API access with Lightning, (2) creating or paying BOLT11 invoices, (3) checking wallet balance or channel health, (4) managing peers and channels.…
lightning-memory
Decentralized agent memory with Nostr identity and Lightning L402 payments.
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts). The work commits land first, then the version bump, verification, and the release commit on top. Stops at "committed locally on main" — or, when the project releases…
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, fast-forwards main when the release rode a release PR, creates the annotated tag on the commit main now points at, pushes commits and tags, then publishes…
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.