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 skills add kolodkin/devpowers --skill setup-mcpgit clone --depth 1 https://github.com/kolodkin/devpowersWrote 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/kolodkin/devpowers/setup-mcp)<a href="https://agentmods.dev/skills/kolodkin/devpowers/setup-mcp"><img src="https://agentmods.dev/badge/skills/kolodkin/devpowers/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/skills/kolodkin/devpowers/setup-mcp"><img src="https://agentmods.dev/badge/skills/kolodkin/devpowers/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.00108 | $0.01687 |
| Opus 5.5 | $0.00043 | $0.00675 |
| Sonnet 5.5 | $0.00022 | $0.00337 |
| Haiku 4.5 | $0.00011 | $0.00169 |
Grade A, and why
setup-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 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.
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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup MCP
Register one of the MCP servers listed in ./mcps.json into either the project's .mcp.json, the user's Claude Code config, or via a manual file edit. The skill is bounded — it will not install MCPs outside the manifest. To add a new server, append an entry to mcps.json first (see "Adding a new MCP" below).
Invocation
/setup-mcp # list known MCPs, prompt to pick one
/setup-mcp <name> # set up the named MCP
Flow
1. Resolve which MCP
Read ./mcps.json. It maps each <name> to its config template, prerequisites, detection tool, and source URL.
- No argument → present a numbered list of
<name> — descriptionand ask the user to pick. <name>in the manifest → use that entry.<name>not in the manifest → tell the user: "<name>isn't in the bounded list. Append an entry toskills/setup-mcp/mcps.jsonfirst, then re-run." Show them an existing entry as a template. Stop — do not search the web for install instructions.
2. Detect whether it's already configured
Two checks:
- Is the entry's
detection_tool(e.g.mcp__github__list_pull_requests) visible in your tool list right now? - Is
<name>already registered? Tryclaude mcp list 2>/dev/nulland grep for it; also check./.mcp.json(if it exists) formcpServers.<name>.
If already configured, report where it's registered and stop. Don't reconfigure unless the user explicitly asks ("force", "reconfigure", "overwrite").
3. Verify prerequisites
For each command in the entry's required_cli, run command -v <cmd> >/dev/null && echo OK || echo MISSING. If anything is missing, surface the entry's notes (which should explain how to install it) and stop. Don't write any config until prerequisites are in place.
4. Show the proposed config
Print the exact JSON snippet that would be added under mcpServers.<name> — i.e. the entry's config_template verbatim. Also list any required_env and auth_alternatives so the user knows which env vars / tokens need to be set in their shell.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 121 lines · 108 tokens per session scan A f837d2ab700c
setup-mcp is a skill published in the GitHub repository kolodkin/devpowers (2 stars, last pushed 2d ago), licensed MIT. It adds 108 tokens to every session and 1,687 once invoked, about $0.0004 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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…