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/drvoss/everything-copilot-cli/mcp-buildernpx skills add drvoss/everything-copilot-cli --skill mcp-buildergit clone --depth 1 https://github.com/drvoss/everything-copilot-cliWhat 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.00043 | $0.01858 |
| Opus 5 | $0.00022 | $0.00929 |
| Sonnet 5 | $0.00009 | $0.00372 |
| Haiku 4.5 | $0.00004 | $0.00186 |
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 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 — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Builder
mcp-ecosystem helps you install and configure existing servers. This skill is for when
you need to build a new MCP server for your own domain, APIs, or internal tools.
Copilot CLI makes that loop faster with native MCP management commands and workspace/user config
surfaces.
Why This is Copilot-Exclusive
Copilot CLI has a practical MCP authoring loop built around:
copilot mcp add— quick user-level server registrationcopilot mcp list/copilot mcp get— inspect what Copilot will load- shared config paths such as workspace
.mcp.json
That shortens the edit → inspect → load → test cycle while you build a server.
When to Use
- You need tools for an internal API, database, or service Copilot cannot reach natively
- Existing MCP servers do not match the workflow you need
- You want a shared MCP server for a team or repository
- You need domain-specific tools with tighter validation than generic servers provide
When NOT to Use
| Instead of mcp-builder | Use |
|---|---|
| Installing an existing MCP server | mcp-ecosystem |
| Using only built-in GitHub tools | built-in GitHub MCP |
| Writing a one-off local script for yourself | a normal script or CLI tool |
Prerequisites
- Clear target users and workflows for the server
- Access to the service or API the server will wrap
- A chosen implementation stack such as TypeScript or Python
- A place to store the MCP config (workspace
.mcp.jsonor user-level config)
Workflow
1. Plan the tool surface
Decide whether the server should expose:
- low-level API coverage
- workflow-oriented tools
- or a mix of both
Use stable, action-oriented tool names such as:
db_querypayments_get_invoicefeature_flags_list
2. Model the inputs and outputs
Every tool should define:
- explicit parameter names
- descriptions with constraints
- predictable output shape
- actionable error messages
For read-only tools, mark the intent clearly in the tool design.
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 · 218 lines · 43 tokens per session scan A 6029415de8a1
mcp-builder is a skill published in the GitHub repository drvoss/everything-copilot-cli (45 stars, last pushed 6d ago), licensed MIT. It adds 43 tokens to every session and 1,858 once invoked, about $0.0002 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
winui-session-report
Analyze the current or a recent agent session (GitHub Copilot CLI or Claude Code) and generate a diagnostic report. Use only when the user explicitly asks for session feedback, agent debugging, or a review of what happened during a build session. Do not inspect session data automatically.
rig
Minimal agent cli harness for defining harnesses in prompts as rig markdown fences.
atifact
This skill should be used when the user asks to "extract agent trajectory", "convert HAR to trajectory", "get trajectory from session", "parse agent session", "convert Claude Code logs", "convert Copilot CLI logs", "extract ATIF", or needs to convert HAR files or JSONL session logs into ATIF trajectory JSON using the…
update-skill-with-log
允许 organizer 和 player 调整 skill，但每次变更都必须同步做文档记录。.
explain-project-design
把这个仓库解释成一个从 coordinator-heavy live loop 演进到 standalone bridge 的版本化多智能体设计。.
ai-ready
ANALYSIS SKILL — Analyze any repository and generate AI-ready configuration — AGENTS.md, copilot-instructions.md, skills, CI workflows, issue templates. WHEN: "make this repo ai-ready", "set up AI config", "add copilot instructions", "prepare this repo for AI contributions", "generate AGENTS.md". INVOKES: glob, grep…