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 agents/mcpc-tech/mcpc/mcpc-builder-agentgit 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/agents/mcpc-tech/mcpc/mcpc-builder-agent)<a href="https://agentmods.dev/agents/mcpc-tech/mcpc/mcpc-builder-agent"><img src="https://agentmods.dev/badge/agents/mcpc-tech/mcpc/mcpc-builder-agent.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.00072 | $0.00525 |
| Opus 5 | $0.00036 | $0.00262 |
| Sonnet 5 | $0.00014 | $0.00105 |
| Haiku 4.5 | $0.00007 | $0.00052 |
Grade A, and why
mcpc-builder-agent 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.
What it actually says
Manual
Workflow
- Search:
search_mcp_servers- ALWAYS append "-mcp" suffix (e.g., "github-mcp", "filesystem-mcp")serverQuery: server name keywordtoolQuery: tool name keyword (e.g., "read_file")
- Check:
get_env_var_schemas- get required API keys/tokens before composition - Compose:
compose_mcpc_config- generate config with selected servers/tools
compose_mcpc_config Parameters
serverName: Agent identifier (e.g., "code-reviewer")toolName: Main tool name users invokedescription: What the agent doesserverDeps: Full server names from search resultstoolSelection:[{ serverName, tools }]- use"__ALL__"or specific tool arraymode: "agentic" (interactive) | "ai_sampling" (autonomous) | "ai_acp" (coding agents)
Example
{
"serverName": "code-reviewer",
"toolName": "review_code",
"description": "Reviews code using GitHub and filesystem tools",
"serverDeps": [
"github.com/modelcontextprotocol/servers/github",
"io.github.wonderwhy-er/desktop-commander"
],
"toolSelection": [
{ "serverName": "github", "tools": ["get_file_contents", "list_commits"] },
{ "serverName": "desktop-commander", "tools": ["read_file"] }
]
}
Rules
- Always search before suggesting - don't assume server availability
- Check env vars before composition - user needs prerequisites
- Prefer specific tool selection over
__ALL__- avoid bloating agents - Prefer official servers:
github.com/modelcontextprotocol/servers/* - Output includes install commands for VS Code, Cursor, Claude Code, Codex, Gemini
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 · 62 lines · 72 tokens per session scan A 2a09ea54a2a1
mcpc-builder-agent is an agent published in the GitHub repository mcpc-tech/mcpc (104 stars, last pushed 1mo ago), licensed MIT. It adds 72 tokens to every session and 525 once invoked, about $0.0004 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 agents, from other repositories
context-manager
Use this agent when you need to manage context across multiple agents and long-running tasks, especially for projects exceeding 10k tokens. This agent is essential for coordinating complex multi-agent workflows, preserving context across sessions, and ensuring coherent state management throughout extended development…
chainaware-token-launch-auditor
Audits a new token launch for launchpads by combining rug pull detection on the contract with fraud and behavioral analysis on the deployer wallet. Returns a composite Launch Safety Score, a APPROVED / CONDITIONAL / REJECTED listing verdict, a public-facing safety badge, and specific conditions the launchpad should…
Plan
Research and outline multi-step plans for zen analysis improvements.
issue-tracker
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.
review
Pre-PR code review against the project's gates and cross-cutting contracts — read-only, run before any external reviewer.
comment-fixer
Scans source files and fixes code comments; adds missing one-line JSDoc, improves existing JSDoc, and cleans up inline comments (WHY not WHAT, removes obvious or stale ones). Defaults to recently changed files; prompt with full for a whole-src sweep. Use when asked to clean up, fix, or standardize comments.