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.
git clone --depth 1 https://github.com/AGoldian/claudenvWrote 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/agoldian/claudenv/setup-mcp)<a href="https://agentmods.dev/commands/agoldian/claudenv/setup-mcp"><img src="https://agentmods.dev/badge/commands/agoldian/claudenv/setup-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/agoldian/claudenv/setup-mcp"><img src="https://agentmods.dev/badge/commands/agoldian/claudenv/setup-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.00009 | $0.01154 |
| Opus 5.5 | $0.00004 | $0.00462 |
| Sonnet 5.5 | $0.00002 | $0.00231 |
| Haiku 4.5 | $0.00001 | $0.00115 |
Grade B, and why
setup-mcp scanned grade B with 2 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 1mo 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 MCP configurationmediumAgent snooping
mcp.json carries server URLs and auth tokens; reading it lets a mod discover and abuse other integrations.
Remind the user that `.mcp.json` is safe to commit — it only contains placeholders, not actual secrets. Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
allowed-tools: Read, Write, Glob, Grep, Bash(curl:*), Bash(find:*), Bash(cat:*) How it starts
The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Server Setup
You are configuring MCP servers for this project. Analyze the tech stack, search the official MCP Registry, verify trust signals, and generate .mcp.json.
Step 1: Analyze the Project
Understand what this project uses:
Read existing documentation:
- Read CLAUDE.md if it exists — it contains the tech stack summary
- Read _state.md if it exists
Check for existing MCP config:
- Read
.mcp.jsonif it exists — you will merge new entries, not overwrite
Scan manifest files:
!find . -maxdepth 3 \( -name "package.json" -o -name "pyproject.toml" -o -name "go.mod" -o -name "Cargo.toml" -o -name "Gemfile" -o -name "composer.json" -o -name "requirements.txt" \) -not -path "*/node_modules/*" -not -path "*/.venv/*" -not -path "*/vendor/*" 2>/dev/null | head -20
Scan framework and tooling configs:
!find . -maxdepth 2 \( -name "tsconfig*.json" -o -name "next.config.*" -o -name "vite.config.*" -o -name "docker-compose.*" -o -name "Dockerfile" -o -name ".env*" -o -name "prisma" -o -name "drizzle.config.*" \) -not -path "*/node_modules/*" 2>/dev/null | head -20
Read the manifest files you found. Identify:
- Programming languages and frameworks
- Databases (PostgreSQL, MongoDB, Redis, etc.)
- Cloud services (AWS, GCP, Azure)
- External APIs (Stripe, Sentry, etc.)
- Dev tools (Docker, GitHub Actions, etc.)
Step 2: Search the MCP Registry
Read the MCP server reference for search and evaluation guidance: @.claude/skills/doc-generator/templates/mcp-servers.md
For each major technology in the project, search the official MCP Registry API:
curl -s 'https://registry.modelcontextprotocol.io/v0.1/servers?search=<tech>&version=latest&limit=10'
For each candidate server with an npm package, verify trust by checking monthly downloads:
curl -s 'https://api.npmjs.org/downloads/point/last-month/<npm-package>'
Optionally check GitHub stars for additional trust signal:
curl -s 'https://api.github.com/repos/<owner>/<repo>'
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.
- 1mo ago First seen · 116 lines · 9 tokens per session scan B 786a3e95d4cc
setup-mcp is a command published in the GitHub repository AGoldian/claudenv (10 stars, last pushed 4mo ago), licensed MIT. It adds 9 tokens to every session and 1,154 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it B with 2 findings (reads mcp configuration, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
doctor
Use when the user invokes /goal-flight doctor to check Goal Flight host and project readiness.
interactive-dev
Start a persistent interactive development session with natural language browser control, auto-error monitoring, and full dev tool access.
graduate
Graduate a Lovable / Bolt / v0 export to GitHub Actions + a non-platform deploy target via the Starter Series 5-step path. Orchestrates the three audit MCP tools and surfaces lift-in steps for the matching starter.
figma-design-to-code
Implement a Figma frame, file, or selection as production code with pixel-exact fidelity.
sugar-review
Review and manage pending Sugar tasks interactively.
sugar-task
Create a comprehensive Sugar task with rich context and metadata.