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/mcpc-tech/mcpc/mcpc-corenpx skills add mcpc-tech/mcpc --skill mcpc-coregit clone --depth 1 https://github.com/mcpc-tech/mcpcWrote 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/mcpc-tech/mcpc/mcpc-core)<a href="https://agentmods.dev/skills/mcpc-tech/mcpc/mcpc-core"><img src="https://agentmods.dev/badge/skills/mcpc-tech/mcpc/mcpc-core.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.1 | $0.00053 | $0.02148 |
| Opus 5 | $0.00026 | $0.01074 |
| Sonnet 5 | $0.00011 | $0.00430 |
| Haiku 4.5 | $0.00005 | $0.00215 |
Grade A, and why
mcpc-core 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 6d 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 — 284 lines — stays where its author put it; the contents beside it link to each section on GitHub.
@mcpc/core — Build Agentic MCP Servers
@mcpc/core lets you compose existing MCP tools into agentic MCP tools. You
write a description that references tools via <tool> XML tags, and MCPC wires
everything up into a working MCP server.
Installation
# Deno (preferred in this repo)
deno add jsr:@mcpc/core
# npm
npm install @mcpc-tech/core
# pnpm (from JSR)
pnpm add jsr:@mcpc/core
Minimal Example
import { mcpc } from "@mcpc/core";
import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
const server = await mcpc(
[{ name: "my-agent", version: "1.0.0" }, { capabilities: { tools: {} } }],
[{
name: "file-agent",
description: `I help manage files.
Available tools:
<tool name="@wonderwhy-er/desktop-commander.read_file"/>
<tool name="@wonderwhy-er/desktop-commander.write_file"/>`,
deps: {
mcpServers: {
"@wonderwhy-er/desktop-commander": {
command: "npx",
args: ["-y", "@wonderwhy-er/desktop-commander@latest"],
transportType: "stdio",
},
},
},
}],
);
await server.connect(new StdioServerTransport());
Core API
mcpc(serverConf, composeConf?, options?)
| Param | Type | Description |
|---|---|---|
serverConf |
[ServerMeta, ServerCapabilities] |
Name/version + capabilities tuple |
composeConf |
ComposeInput[] |
Array of ComposeDefinition objects or .md file paths |
options |
McpcOptions |
Loader plugins + setup callback |
Returns Promise<ComposableMCPServer>.
ComposeDefinition
{
name: string | null, // null = composition-only (no tool exposed)
description?: string, // Natural language + <tool> XML refs
manual?: string, // Progressive disclosure: long docs hidden behind man tool
deps?: MCPSetting, // Dependent MCP servers to connect
plugins?: (ToolPlugin | string)[], // Runtime plugins
options?: {
mode?: "agentic" | "ai_sampling" | "ai_acp", // default: "agentic"
maxSteps?: number, // default: 50
maxTokens?: number, // default: 128_000 (ai_sampling only)
samplingConfig?: SamplingConfig,
providerOptions?: { modelPreferences?: {...} }, // ai_sampling only
acpSettings?: { command, args, env, session, persistSession }, // ai_acp only
tracingEnabled?: boolean, // OpenTelemetry
refs?: ToolRefXml[],
}
}
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.
- 6d ago First seen · 284 lines · 53 tokens per session scan A 968771a88a2a
mcpc-core is a skill published in the GitHub repository mcpc-tech/mcpc (104 stars, last pushed 1mo ago), licensed MIT. It adds 53 tokens to every session and 2,148 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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
specflow-use
To connect Rosetta with Grid Dynamics SpecFlow MCP; only when SpecFlow is mentioned and the MCP is installed.
opik-diagnose
Surface the Opik traces worth a developer's attention, ranked by signal — errors, failed tool calls, latency, regressions, and low online-eval scores — plus Diagnostics issues. Reads live/production traces via the SDK (searchtraces and agentinsights) and works with no MCP; uses the MCP issue entity when connected.…
planning-and-task-breakdown
Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.
qa-knowledge
To run QA engineering — requirements/gap analysis, scenario & spec design, test implementation, failure triage — over the QA knowledge base.
ue-mcp-epic-routing
Use when deciding between ue-mcp's native category actions and Epic's wrapped ToolsetRegistry tools (the epic actions, incl. the Blueprint graph DSL) for a task in Unreal. Pulls in when authoring Blueprint graph bodies, or any time both a native action and an epic action could do the job and you need to pick.