Borrowing it
Nothing to install: this file belongs to nerfels/mind-map. 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/nerfels/mind-map/master/.claude/commands/publish-mcp.mdgit clone --depth 1 https://github.com/nerfels/mind-mapWrote 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/commands/nerfels/mind-map/publish-mcp)<a href="https://agentmods.dev/commands/nerfels/mind-map/publish-mcp"><img src="https://agentmods.dev/badge/commands/nerfels/mind-map/publish-mcp/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/commands/nerfels/mind-map/publish-mcp"><img src="https://agentmods.dev/badge/commands/nerfels/mind-map/publish-mcp.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.00011 | $0.01262 |
| Opus 5.5 | $0.00004 | $0.00505 |
| Sonnet 5.5 | $0.00002 | $0.00252 |
| Haiku 4.5 | $0.00001 | $0.00126 |
Grade A, and why
publish-mcp 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 2mo 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🧠 Mind Map MCP Release Workflow
Automated release workflow specifically for the Mind Map MCP project.
Usage
/publish-mcp patch # 1.3.0 → 1.3.1
/publish-mcp minor # 1.3.0 → 1.4.0
/publish-mcp major # 1.3.0 → 2.0.0
/publish-mcp 1.5.2 # Set specific version
Pre-Release Checks
1. Check Git Status
!echo "🔍 Checking git status..." && git status --porcelain
2. Ensure Clean Working Directory
!if [ -n "$(git status --porcelain)" ]; then echo "❌ Working directory not clean. Commit or stash changes first."; exit 1; else echo "✅ Working directory clean"; fi
3. Ensure on Main Branch
!CURRENT_BRANCH=$(git branch --show-current) && if [ "$CURRENT_BRANCH" != "master" ] && [ "$CURRENT_BRANCH" != "main" ]; then echo "❌ Not on main/master branch. Currently on: $CURRENT_BRANCH"; exit 1; else echo "✅ On main branch: $CURRENT_BRANCH"; fi
Release Process
4. Update Version in package.json
!echo "📦 Updating version..." && npm version $1 --no-git-tag-version
5. Get New Version Number
!NEW_VERSION=$(node -p "require('./package.json').version") && echo "🔢 New version: v$NEW_VERSION"
6. Update README.md Version References
!NEW_VERSION=$(node -p "require('./package.json').version") && echo "📝 Updating README version references..." && sed -i.bak "s/mind-map-mcp@[0-9]\+\.[0-9]\+\.[0-9]\+/mind-map-mcp@$NEW_VERSION/g" README.md && sed -i.bak "s/v[0-9]\+\.[0-9]\+\.[0-9]\+/v$NEW_VERSION/g" README.md && rm -f README.md.bak
7. Update PROJECT_PLAN.md if exists
!NEW_VERSION=$(node -p "require('./package.json').version") && if [ -f "PROJECT_PLAN.md" ]; then echo "📋 Updating PROJECT_PLAN.md..." && sed -i.bak "s/v[0-9]\+\.[0-9]\+\.[0-9]\+/v$NEW_VERSION/g" PROJECT_PLAN.md && rm -f PROJECT_PLAN.md.bak; else echo "📋 No PROJECT_PLAN.md found, skipping..."; fi
8. Build Project
!echo "🔨 Building project..." && npm run build
9. Run TypeScript Check
!echo "📘 Running TypeScript check..." && npx tsc --noEmit
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.
- 2mo ago First seen · 79 lines · 11 tokens per session scan A 1bacf49ea126
publish-mcp is a command published in the GitHub repository nerfels/mind-map (2 stars, last pushed 11mo ago), licensed MIT. It adds 11 tokens to every session and 1,262 once invoked, about $0.0000 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 commands, from other repositories
land
Resolve and squash merge one named, currently authorized pull request.
quality
A command for temporarily clearing a release quality gate or one named check, while recording the reason and expiry time. A quality gate is a required check that normally blocks completion or release.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and the open issues it resolves.