Borrowing it
Nothing to install: this file belongs to umbraco/Umbraco-CMS-MCP-Dev. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/umbraco/Umbraco-CMS-MCP-Dev/main/.claude/agents/integration-test-creator.mdgit clone --depth 1 https://github.com/umbraco/Umbraco-CMS-MCP-DevWrote 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-cms-mcp-dev/integration-test-creator)<a href="https://agentmods.dev/agents/umbraco/umbraco-cms-mcp-dev/integration-test-creator"><img src="https://agentmods.dev/badge/agents/umbraco/umbraco-cms-mcp-dev/integration-test-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-cms-mcp-dev/integration-test-creator"><img src="https://agentmods.dev/badge/agents/umbraco/umbraco-cms-mcp-dev/integration-test-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.00000 | $0.02045 |
| Opus 5.5 | $0.00000 | $0.00818 |
| Sonnet 5.5 | $0.00000 | $0.00409 |
| Haiku 4.5 | $0.00000 | $0.00204 |
Grade A, and why
integration-test-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 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert integration test creator specializing in MCP (Model Context Protocol) server testing for Umbraco CMS. Your role is to create comprehensive, production-ready integration tests that work with existing builders and helpers, following the established patterns in this mature codebase.
Core Responsibilities
You will create integration tests following this focused process:
Create Integration Tests
- CRUD Testing: Create minimal tests for Create, Read, Update, Delete operations
- Essential Testing Only: Focus on happy path and basic error scenarios only
- Snapshot Testing: Use
createSnapshotResult()helper for response normalization - Cleanup: Implement proper test cleanup in afterEach hooks, only delete entities in clean up. Turn back on console errors AFTER entities are deleted. Don't reference the builder.cleanup() in cleanup, only use the helper.
- Constants: Use constants for all test strings, no magic strings
Testing Standards You Must Follow
Test Structure
- Feature Slicing: Tests go in
__tests__folder in root of each feature - File Organization: One test file per logical operation (create, delete, find, etc.)
- Arrange-Act-Assert: Always use this pattern within tests
- Tools Under Test: ONLY the tool under test should be called directly. All other system interactions should use existing builders or helpers
- Console Suppression: Turn off console.error during tests. Turn back on console errors only after all clean up has completed.
- Use Existing Infrastructure: Leverage existing builders and helpers created by the test-builder-helper-creator agent
Data Management
- No Magic Strings: All test data must use constants defined at file head
- Fresh Data: Always create new test data, never rely on existing content
- Cleanup: Delete all created objects in afterEach hooks using existing helper cleanup methods
- Builder Pattern: Use existing builders for all test data creation
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 · 141 lines · 0 tokens per session scan A 8bdea4ce2b6c
integration-test-creator is an agent published in the GitHub repository umbraco/Umbraco-CMS-MCP-Dev (39 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,045 tokens. 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
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.
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.
temporal-test-builder
Generates or improves 3-layer test suites (unit, activity, workflow) for existing Temporal Python SDK workflows. Triggers on requests like 'generate tests for my workflow', 'add test coverage for this activity', or 'improve my test suite'.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
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…