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 commands/superclaude-org/superclaude_plugin/setup-mcpgit clone --depth 1 https://github.com/SuperClaude-Org/SuperClaude_PluginWrote 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/superclaude-org/superclaude_plugin/setup-mcp)<a href="https://agentmods.dev/commands/superclaude-org/superclaude_plugin/setup-mcp"><img src="https://agentmods.dev/badge/commands/superclaude-org/superclaude_plugin/setup-mcp.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 | $0.00005 | $0.01380 |
| Opus 5 | $0.00003 | $0.00690 |
| Sonnet 5 | $0.00001 | $0.00276 |
| Haiku 4.5 | $0.00001 | $0.00138 |
Grade B, and why
setup-mcp scanned grade B with 1 finding 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 4d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
if [ -f ~/.claude/settings.local.json ]; then How it starts
The opening of the file, as written. The whole thing — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sc:setup-mcp - MCP Server Setup Wizard
You are now in MCP Setup Wizard Mode. Guide the user through checking prerequisites, verifying the automatic MCP configuration, and setting up optional features.
Setup Process
Step 1: Welcome & Overview
Explain the MCP server architecture:
🚀 SuperClaude MCP Setup Wizard
SuperClaude plugin automatically configures AIRIS MCP Gateway, which provides
unified access to 10 powerful tools:
Essential (Free):
• sequential-thinking - Multi-step problem solving
• context7 - Official documentation search
• git - Repository operations
• puppeteer - Browser automation
• playwright - Cross-browser testing
• chrome-devtools - Browser debugging
Optional (API Key Required):
• tavily - Web search ($)
• magic - UI component generation ($)
• serena - Context-aware intelligence
• morphllm - Multi-model orchestration
Let's verify your setup...
Step 2: Backup Existing MCP Configuration (Safety First!)
IMPORTANT: Before proceeding, check if the user has existing MCP servers configured.
# Check for existing MCP configuration
if [ -f ~/.claude/settings.local.json ]; then
echo "⚠️ Found existing Claude Code settings"
echo ""
echo "RECOMMENDED: Backup your settings before enabling the plugin:"
echo " cp ~/.claude/settings.local.json ~/.claude/settings.local.json.backup"
echo ""
read -p "Have you backed up your settings? (y/n): " backup_done
if [ "$backup_done" != "y" ]; then
echo ""
echo "Creating backup now..."
cp ~/.claude/settings.local.json ~/.claude/settings.local.json.backup
echo "✅ Backup created: ~/.claude/settings.local.json.backup"
fi
else
echo "✅ No existing settings found (fresh installation)"
fi
# Check for project-specific MCP config
if [ -f .mcp.json ]; then
echo ""
echo "⚠️ Found project-specific MCP configuration (.mcp.json)"
echo "RECOMMENDED: Backup before proceeding:"
echo " cp .mcp.json .mcp.json.backup"
fi
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.
- 4d ago First seen · 219 lines · 5 tokens per session scan B 2750a029cf52
setup-mcp is a command published in the GitHub repository SuperClaude-Org/SuperClaude_Plugin (55 stars, last pushed 13d ago), licensed MIT. It adds 5 tokens to every session and 1,380 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.