Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/umbraco/Umbraco-MCP-Basenpx agentmods add skills/umbraco/umbraco-mcp-base/build-evalsWrote 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/umbraco/umbraco-mcp-base/build-evals)<a href="https://agentmods.dev/skills/umbraco/umbraco-mcp-base/build-evals"><img src="https://agentmods.dev/badge/skills/umbraco/umbraco-mcp-base/build-evals/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/umbraco/umbraco-mcp-base/build-evals"><img src="https://agentmods.dev/badge/skills/umbraco/umbraco-mcp-base/build-evals.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.00036 | $0.03279 |
| Opus 5.5 | $0.00014 | $0.01312 |
| Sonnet 5.5 | $0.00007 | $0.00656 |
| Haiku 4.5 | $0.00004 | $0.00328 |
Grade A, and why
build-evals 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 2mo 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 — 379 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build Evals
Generate LLM eval tests for MCP tool collections created by /build-tools. This skill reads .discover.json and the existing tool files, then builds eval test files in tests/evals/ one collection at a time.
IMPORTANT: This skill ONLY creates files inside tests/evals/ — the setup file and eval test files. Do NOT create or modify tool files, collection indexes, integration tests, mock handlers, or any other files.
Key difference from integration tests (/build-tools-tests):
- Integration tests: one file per tool, test handlers directly against real API, deterministic
- Eval tests: group related tools by workflow, test via Claude Agent SDK, probabilistic, require
npm run buildfirst (run againstdist/)
Prerequisites
Before running, ensure:
- You have run
/build-tools(tool collections exist insrc/umbraco-api/tools/) - The project builds:
npm run build - An LLM API key is available (eval tests use Claude Agent SDK — works with a Claude Code subscription or
ANTHROPIC_API_KEY)
Arguments
- No arguments: build evals for all collections from
.discover.json - Single collection name: build evals only for that collection (e.g.
/build-evals form)
Agents
This skill orchestrates the following agent — use it for the relevant step:
| Agent | When to use |
|---|---|
eval-test-creator |
Creating eval test files (Step 5) |
Critical Rules
BUILD BEFORE RUNNING. Eval tests run against dist/index.js. Always npm run build first.
ONE COLLECTION AT A TIME. Complete each collection before starting the next.
GROUP TOOLS BY WORKFLOW. Unlike integration tests (one file per tool), eval tests group related tools into workflow scenarios. A collection with 5 tools might have just 1-2 eval test files.
ITERATE ON PROMPTS. Eval tests are probabilistic. If a test fails, the fix is usually in the prompt — make instructions more explicit, add search steps for IDs, use unique identifiers.
VERBOSE DURING DEVELOPMENT. Always set verbose: true when creating/debugging. Disable after tests pass reliably.
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.
- 2mo ago First seen · 379 lines · 36 tokens per session scan A e31b6e0a5fc1
build-evals is a skill published in the GitHub repository umbraco/Umbraco-MCP-Base (2 stars, last pushed yesterday), licensed MIT. It adds 36 tokens to every session and 3,279 once invoked, about $0.0001 per session on Opus 5.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.
build-evals compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| build-evalsumbraco/Umbraco-MCP-Base | Skill | 2 | yesterday | MIT | A | 36 | Claude Code |
| imagegenopenai/codex | Skill | 135k | today | Apache-2.0 | A | 113 | Codex |
| playwright-climicrosoft/playwright | Skill | 100k | today | Apache-2.0 | A | 19 | Claude Code |
| browser-automationopenclaw/openclaw | Skill | 394k | today | MIT | A | 36 | Claude Code |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 80k | 6d ago | MIT | A | 200 | Claude Code, Codex |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | today | MIT | A | 95 | Claude Code |
| chat-pet-sprite-creationmicrosoft/vscode | Skill | 195k | today | MIT | A | 53 | Claude Code, Codex |