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 skills/emdashcodes/claude-code-plugins/claude-code-mcpnpx skills add emdashcodes/claude-code-plugins --skill claude-code-mcpgit clone --depth 1 https://github.com/emdashcodes/claude-code-pluginsWhat 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.00051 | $0.03655 |
| Opus 5 | $0.00026 | $0.01827 |
| Sonnet 5 | $0.00010 | $0.00731 |
| Haiku 4.5 | $0.00005 | $0.00365 |
Grade A, and why
claude-code-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 2d 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 — 614 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code MCP Configuration
Guide Claude through configuring and managing MCP (Model Context Protocol) servers to connect Claude Code with external tools, databases, and services.
Purpose
MCP servers enable Claude Code to interact with external tools and data sources through a standardized protocol. This skill helps install, configure, and manage MCP servers across different scopes (local, project, user), authenticate with remote services, and troubleshoot connection issues.
When to Use This Skill
Use this skill when:
- Installing MCP servers (HTTP, SSE, or stdio transport)
- Configuring MCP server authentication and environment variables
- Managing MCP server scopes (local, project, user)
- Troubleshooting MCP server connectivity or authentication issues
- Setting up team-wide MCP server configurations
- Importing MCP servers from Claude Desktop
- Using MCP resources and prompts in conversations
Do NOT use this skill for:
- Creating or building MCP servers (use MCP SDK documentation instead)
- Writing MCP server code (this skill is for configuration only)
MCP Server Transports
MCP servers can connect using three transport mechanisms:
HTTP Transport (Recommended)
Best for cloud-based services with REST APIs.
Basic syntax:
claude mcp add --transport http <name> <url>
Examples:
# Simple HTTP server
claude mcp add --transport http notion https://mcp.notion.com/mcp
# With authentication header
claude mcp add --transport http secure-api https://api.example.com/mcp \
--header "Authorization: Bearer your-token"
# With custom headers
claude mcp add --transport http custom-api https://api.example.com/mcp \
--header "X-API-Key: key123" \
--header "X-Custom-Header: value"
SSE Transport (Deprecated)
Server-Sent Events transport. Use HTTP where available.
Basic syntax:
claude mcp add --transport sse <name> <url>
Example:
claude mcp add --transport sse asana https://mcp.asana.com/sse
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.
- 2d ago First seen · 614 lines · 51 tokens per session scan A b52212af3c54
claude-code-mcp is a skill published in the GitHub repository emdashcodes/claude-code-plugins (13 stars, last pushed 1mo ago), licensed MIT. It adds 51 tokens to every session and 3,655 once invoked, about $0.0003 per session on Opus 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…