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/poorgramer-zack/copilot-cli-things/mcp-buildernpx skills add Poorgramer-Zack/copilot-cli-things --skill mcp-buildergit clone --depth 1 https://github.com/Poorgramer-Zack/copilot-cli-thingsWrote 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/poorgramer-zack/copilot-cli-things/mcp-builder)<a href="https://agentmods.dev/skills/poorgramer-zack/copilot-cli-things/mcp-builder"><img src="https://agentmods.dev/badge/skills/poorgramer-zack/copilot-cli-things/mcp-builder.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.00057 | $0.01929 |
| Opus 5 | $0.00028 | $0.00964 |
| Sonnet 5 | $0.00011 | $0.00386 |
| Haiku 4.5 | $0.00006 | $0.00193 |
Grade A, and why
MCP Builder 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 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.
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 — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Server Development Guide
Build MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools.
Deliverables: working MCP server with well-designed tools, clear tool descriptions/input schemas/annotations, evaluation suite, and setup documentation.
Phase 1: Deep Research and Planning
1.1 Understand Modern MCP Design
API Coverage vs. Workflow Tools: Balance comprehensive API endpoint coverage with specialized workflow tools. When uncertain, prioritize comprehensive API coverage — it gives agents flexibility to compose operations.
Tool Naming and Discoverability:
- Use
snake_casewith service prefix:{service}_{action}_{resource} - Examples:
slack_send_message,github_create_issue - Be action-oriented: start with verbs (get, list, search, create, update, delete)
Context Management: Design tools that return focused, relevant data. Support pagination and filtering to avoid overwhelming responses.
Actionable Error Messages: Error messages should guide agents toward solutions with specific suggestions and next steps.
1.2 Study MCP Protocol
Start with the sitemap: https://modelcontextprotocol.io/sitemap.xml
Fetch specific pages with .md suffix (e.g., https://modelcontextprotocol.io/specification/draft.md).
Key pages: specification overview, transport mechanisms (streamable HTTP, stdio), tool/resource/prompt definitions.
1.3 Choose Framework
Recommended stack:
- Language: TypeScript (strong SDK support, good AI code generation, static typing)
- Transport: Streamable HTTP for remote servers (stateless JSON), stdio for local servers
Framework documentation:
- 📋 MCP Best Practices — Core guidelines (load first)
- ⚡ TypeScript Guide — TypeScript patterns with
@modelcontextprotocol/sdk - 🐍 Python Guide — Python patterns with FastMCP
What ships with it
9 files 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.
- examples/example-evaluation.xml 1.5 KB
- references/evaluation-guide.md 22 KB
- references/mcp-best-practices.md 7.4 KB
- references/node-mcp-server.md 29 KB
- references/python-mcp-server.md 25 KB
- scripts/connections.py 4.8 KB runs code
- scripts/evaluation.py 12 KB runs code
- scripts/README.md 1.0 KB
- scripts/requirements.txt 29 B
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 · 232 lines · 57 tokens per session scan A 7806462366b7
MCP Builder is a skill published in the GitHub repository Poorgramer-Zack/copilot-cli-things (2 stars, last pushed 5mo ago), licensed MIT. It adds 57 tokens to every session and 1,929 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-31.
Other skills, from other repositories
speckit-init
Scaffold a Spec Kit (spec-driven development) project for GitHub Copilot by running specify init --integration copilot --integration-options="--skills". USE FOR: starting a new spec-kit project, bootstrapping spec-driven development in an existing repo, installing spec-kit templates/scripts/commands for Copilot. DO…
speckit-bundle
Discover, install, and author Spec Kit bundles via specify bundle. USE FOR: searching/showing/listing bundles, installing/updating/removing a bundle (a curated set of extensions/presets/integrations/workflows), validating a bundle manifest, building a distributable bundle artifact, initializing a project and…
speckit-extension
Manage Spec Kit extensions via specify extension. USE FOR: installing/removing/updating spec-kit extensions, searching the extension catalog, showing extension info, enabling/disabling extensions, setting extension resolution priority, managing extension catalogs. DO NOT USE FOR: presets (use speckit-preset), bundles…
speckit-preset
Manage Spec Kit presets via specify preset. USE FOR: installing/removing presets, searching the preset catalog, showing preset info, resolving which template a preset name maps to, enabling/disabling presets, setting preset resolution priority, managing preset catalogs. DO NOT USE FOR: extensions (use…
speckit-workflow
Manage and run Spec Kit automation workflows via specify workflow. USE FOR: running a workflow by ID or local YAML, resuming a paused/failed run, checking run status, listing/installing/removing workflows, searching the workflow catalog, showing a workflow step graph. DO NOT USE FOR: extensions (use…
speckit-check
Check the local environment for Spec Kit by running specify check (and specify version). USE FOR: verifying required tools are installed, diagnosing a broken spec-kit setup, reporting CLI version/feature capabilities. DO NOT USE FOR: installing or upgrading the CLI itself (use the speckit-self skill).