What is build-tools-tests?

A generator for integration tests for collections of MCP tools. Integration tests check that tools work correctly with the surrounding server and services.

Use it after building Umbraco MCP tools to create test setup, builders, helpers, and collection-specific integration tests. It works only within test directories.

Writing the setup, test helpers, and repeated test structures by hand takes time and can lead to inconsistent coverage. This creates those test files from the project's discovered tool collections.

build-tools-tests — Skill for Claude Code by umbraco

Install

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.

Clone the repo

git clone --depth 1 https://github.com/umbraco/Umbraco-MCP-Base

agentmods

npx agentmods add skills/umbraco/umbraco-mcp-base/build-tools-tests

Made for: Claude Code.

Or install umbraco-mcp-skills, the plugin that ships this one along with the rest of its 13 skills, 7 agents.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/umbraco/umbraco-mcp-base/build-tools-tests/github.svg)](https://agentmods.dev/skills/umbraco/umbraco-mcp-base/build-tools-tests)

Your own site

<a href="https://agentmods.dev/skills/umbraco/umbraco-mcp-base/build-tools-tests"><img src="https://agentmods.dev/badge/skills/umbraco/umbraco-mcp-base/build-tools-tests/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/umbraco/umbraco-mcp-base/build-tools-tests"><img src="https://agentmods.dev/badge/skills/umbraco/umbraco-mcp-base/build-tools-tests.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 5,450 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00038	$0.05450
Opus 5	$0.00019	$0.02725
Sonnet 5	$0.00008	$0.01090
Haiku 4.5	$0.00004	$0.00545

Measured 12d ago against content hash 50797b6ee222, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

build-tools-tests 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 12d 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.

plugins/umbraco-mcp-skills/skills/build-tools-tests/SKILL.md · 566 lines

How it starts

The opening of the file, as written. The whole thing — 566 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Build Tests

Generate integration tests for MCP tool collections created by /build-tools. This skill reads .discover.json and the existing tool files, then builds test infrastructure and test files one collection at a time.

IMPORTANT: This skill ONLY creates files inside __tests__/ directories — test files, setup, builders, and helpers. Do NOT create or modify ANY other files. This means: no tool files, no collection indexes, no registrations, no API client files (src/umbraco-api/api/), no generated code (src/umbraco-api/api/generated/), no mock handlers (src/mocks/). If existing code doesn't support what you need, work within the constraints — do not modify it.

Prerequisites

Before running, ensure:

You have run /build-tools (tool collections exist in src/umbraco-api/tools/)
The project compiles: npm run compile
The Umbraco instance is running
An API user exists — remind the user: "You need to create an API user via the Umbraco backoffice UI: Settings > Users, with Client ID umbraco-back-office-mcp and Client Secret 1234567890"

Arguments

No arguments: build tests for all collections from .discover.json
Single collection name: build tests only for that collection (e.g. /build-tools-tests form)

Agents

This skill orchestrates the following agents — use them for the relevant steps:

Agent	When to use
`test-builder-helper-creator`	Creating builders and helpers (Steps 4-5)
`integration-test-creator`	Creating test files (Step 7)
`integration-test-validator`	Validating test quality (Step 8)

Critical Rules

ONE FILE AT A TIME. This applies to ALL files — builders, helpers, builder tests, and tool tests. After creating any file:

Compile: npm run compile
If it has tests, run them: npm test -- path/to/file.test.ts
Fix any failures
Only then create the next file

RUN COMMANDS SEPARATELY. Always run compile and test as separate Bash calls. Never chain them with &&.

Read the full file on GitHub · 566 lines

Files

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.

instance-management.md 5.9 KB

Changes

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.

12d ago First seen · 566 lines · 38 tokens per session scan A 50797b6ee222

Subscribe to this mod's changes

build-tools-tests is a skill published in the GitHub repository umbraco/Umbraco-MCP-Base (2 stars, last pushed yesterday), licensed MIT. It adds 38 tokens to every session and 5,450 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-31.

Testing

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

tika-eval-compare

Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".

apache/tika · 50 tokens

neuron-evaluation-engineer

Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…

neuron-core/neuron-ai · 77 tokens

build-tools-tests