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 skills add greynewell/mcpbr --skill mcpbr-configgit clone --depth 1 https://github.com/greynewell/mcpbrWrote 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/greynewell/mcpbr/mcpbr-config)<a href="https://agentmods.dev/skills/greynewell/mcpbr/mcpbr-config"><img src="https://agentmods.dev/badge/skills/greynewell/mcpbr/mcpbr-config/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/greynewell/mcpbr/mcpbr-config"><img src="https://agentmods.dev/badge/skills/greynewell/mcpbr/mcpbr-config.svg" alt="Reviewed on agentmods" width="80" 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.00016 | $0.01429 |
| Opus 5 | $0.00008 | $0.00714 |
| Sonnet 5 | $0.00003 | $0.00286 |
| Haiku 4.5 | $0.00002 | $0.00143 |
Grade A, and why
generate-config 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 10d 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 — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Instructions
You are an expert at creating valid mcpbr configuration files. Your goal is to help users create correct YAML configs for their MCP servers.
Critical Requirements
-
Always Include {workdir} Placeholder: The
argsarray MUST include"{workdir}"as a placeholder for the task repository path. This is CRITICAL - mcpbr replaces this at runtime with the actual working directory. -
Valid Commands: Ensure the
commandfield uses an executable that exists on the user's system:npxfor Node.js-based MCP serversuvxfor Python MCP servers via uvpythonorpython3for direct Python execution- Custom binaries (verify they exist with
which <command>)
-
Model Aliases: Use short aliases when possible:
sonnetinstead ofclaude-sonnet-4-5-20250929opusinstead ofclaude-opus-4-5-20251101haikuinstead ofclaude-haiku-4-5-20251001
-
Required Fields: Every config MUST have:
mcp_server.commandmcp_server.args(with"{workdir}")provider(usually"anthropic")agent_harness(usually"claude-code")modeldataset(or rely on benchmark default)
Common MCP Server Configurations
Anthropic Filesystem Server
mcp_server:
name: "filesystem"
command: "npx"
args:
- "-y"
- "@modelcontextprotocol/server-filesystem"
- "{workdir}"
env: {}
Custom Python MCP Server
mcp_server:
name: "my-server"
command: "uvx"
args:
- "my-mcp-server"
- "--workspace"
- "{workdir}"
env:
LOG_LEVEL: "debug"
Supermodel Codebase Analysis
mcp_server:
name: "supermodel"
command: "npx"
args:
- "-y"
- "@supermodeltools/mcp-server"
env:
SUPERMODEL_API_KEY: "${SUPERMODEL_API_KEY}"
Configuration Template
When generating a new config, use this template:
mcp_server:
name: "<server-name>"
command: "<executable>"
args:
- "<arg1>"
- "<arg2>"
- "{workdir}" # CRITICAL: Include this placeholder
env: {}
provider: "anthropic"
agent_harness: "claude-code"
model: "sonnet" # or "opus", "haiku"
dataset: "SWE-bench/SWE-bench_Lite" # or null to use benchmark default
sample_size: 5
timeout_seconds: 300
max_concurrent: 4
max_iterations: 30
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.
- 10d ago First seen · 205 lines · 16 tokens per session scan A 8b13f5ff9550
generate-config is a skill published in the GitHub repository greynewell/mcpbr (10 stars, last pushed 4mo ago), licensed MIT. It adds 16 tokens to every session and 1,429 once invoked, about $0.0001 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
api-testing
Testing patterns for MCP tool/resource handlers using createMockContext and Vitest. Covers mock context options, handler testing, McpError assertions, format testing, Vitest config setup, and test isolation conventions.
add-test
Scaffold a test file for an existing tool, resource, or service. Use when the user asks to add tests, improve coverage, or when a definition exists without a matching test file.
SmartHome Video Anomaly Benchmark
VLM evaluation suite for video anomaly detection in smart home camera footage.
bug-reproducer
Find likely software bugs in a codebase, rank concrete bug candidates, and prove or reject them with focused regression tests before proposing a fix. Also turn bug reports, stack traces, screenshots, failing behavior, support tickets, and regressions into minimal reproducible cases with red-to-green evidence. Use when…
Home Security AI Benchmark
LLM & VLM evaluation suite for home security AI applications.
email-formatting
Markdown formatting conventions for email summary documents — heading depth, list style, line length, emoji policy, and a mandatory provenance footer. Read this when producing a markdown report that summarizes one or more email messages so the output matches the project's house style.