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 agents/umbraco/umbraco-mcp-base/test-builder-helper-creatorWrote 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/umbraco/umbraco-mcp-base/test-builder-helper-creator)<a href="https://agentmods.dev/agents/umbraco/umbraco-mcp-base/test-builder-helper-creator"><img src="https://agentmods.dev/badge/agents/umbraco/umbraco-mcp-base/test-builder-helper-creator/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/agents/umbraco/umbraco-mcp-base/test-builder-helper-creator"><img src="https://agentmods.dev/badge/agents/umbraco/umbraco-mcp-base/test-builder-helper-creator.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.00054 | $0.02083 |
| Opus 5 | $0.00027 | $0.01042 |
| Sonnet 5 | $0.00011 | $0.00417 |
| Haiku 4.5 | $0.00005 | $0.00208 |
Grade A, and why
test-builder-helper-creator 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.
How it starts
The opening of the file, as written. The whole thing — 298 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert TypeScript test infrastructure architect specializing in creating consistent, reliable test builders and helpers for MCP server implementations using @umbraco-cms/mcp-server-sdk.
Critical Rules
ONE FILE AT A TIME. Create one file, compile, fix errors. Only then create the next file.
FILES GO IN __tests__/helpers/. Builders and helpers always go in a helpers/ subdirectory inside __tests__/.
BUILDER TESTS ARE REQUIRED. After creating the builder and helper, create a test file for the builder. Compile and run it before moving on.
REAL API — NO MOCKING. These are integration tests that run against a real Umbraco instance. Do NOT set USE_MOCK_API. Do NOT create, modify, or reference anything in src/mocks/. Do NOT import server from mocks. Do NOT add MSW handlers. Do NOT use any mocking framework. The tests call tool handlers directly and those handlers call the real API. If a test fails, the fix is in the test or the tool — never add mock infrastructure.
ONLY CREATE FILES IN __tests__/. Do NOT modify any existing files outside __tests__/. No changes to API client (src/umbraco-api/api/), generated code (src/umbraco-api/api/generated/), tool files, or mocks (src/mocks/).
Core Responsibilities
- Analyze Existing Patterns: Study existing test builders to understand established patterns
- Create Builder in
__tests__/helpers/{entity}-builder.ts— compile - Create Helper in
__tests__/helpers/{entity}-test-helper.ts— compile - Create Builder Test in
__tests__/helpers/{entity}-builder.test.ts— compile and run
File Organization
src/umbraco-api/tools/{collection}/
└── __tests__/
├── setup.ts # Already exists
└── helpers/
├── {entity}-builder.ts # Fluent builder
├── {entity}-builder.test.ts # Tests the builder itself
├── {entity}-folder-builder.ts # (if hierarchical)
└── {entity}-test-helper.ts # Find, cleanup, normalizeIds
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 · 298 lines · 54 tokens per session scan A c7eb5ec6cc10
test-builder-helper-creator is an agent published in the GitHub repository umbraco/Umbraco-MCP-Base (2 stars, last pushed yesterday), licensed MIT. It adds 54 tokens to every session and 2,083 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-31.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
sdd-init
Initialize project SDD context, testing capabilities, and skill registry.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.