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 umbraco/Umbraco-MCP-Base --skill run-e2egit clone --depth 1 https://github.com/umbraco/Umbraco-MCP-BaseWrote 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/run-e2e)<a href="https://agentmods.dev/skills/umbraco/umbraco-mcp-base/run-e2e"><img src="https://agentmods.dev/badge/skills/umbraco/umbraco-mcp-base/run-e2e/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/run-e2e"><img src="https://agentmods.dev/badge/skills/umbraco/umbraco-mcp-base/run-e2e.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.00078 | $0.00869 |
| Opus 5 | $0.00039 | $0.00434 |
| Sonnet 5 | $0.00016 | $0.00174 |
| Haiku 4.5 | $0.00008 | $0.00087 |
Grade A, and why
run-e2e scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
for i in $(seq 1 24); do if curl -sk -o /dev/null -w '%{http_code}' https://localhost:44374 --max-time 5 | grep -q '200\|302'; then echo "Umbraco is ready"; exit 0; fi; echo "Waiting for Umbraco... (attempt $i/24)"; slee How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run E2E Tests
Playwright-based E2E tests that drive the MCP Inspector UI through the full OAuth flow against the real Forms worker (src/worker.ts), which includes both Forms tool collections and in-process CMS chaining.
Key files:
- Test file:
tests/forms-hosted-e2e/e2e/mcp-inspector.test.ts - Worker setup:
tests/forms-hosted-e2e/e2e/helpers/worker-setup.ts - Wrangler config:
tests/forms-hosted-e2e/wrangler.e2e.toml - Shared test helpers from
@umbraco-cms/mcp-hosted/testing
Steps
1. Check prerequisites
- Verify
demo-site/exists (has a.csprojfile). If not, tell the user to runnpx create-umbraco-mcp-server init.
2. Kill stale processes
Kill any stale processes on the E2E ports (Umbraco, Worker, Inspector):
npm run kill:e2e-ports
Tell the user which stale processes were found and killed.
3. Build the project
Build the worker before running tests:
npm run build
4. Start Umbraco as a background subprocess
Start Umbraco using the existing npm script with run_in_background: true:
npm run start:umbraco
Then wait for Umbraco to be ready. Run this single bash command which loops until the health check succeeds (up to 120 seconds):
for i in $(seq 1 24); do if curl -sk -o /dev/null -w '%{http_code}' https://localhost:44374 --max-time 5 | grep -q '200\|302'; then echo "Umbraco is ready"; exit 0; fi; echo "Waiting for Umbraco... (attempt $i/24)"; sleep 5; done; echo "Umbraco failed to start within 120s"; exit 1
Tell the user you're waiting for Umbraco to start. If the health check fails after 120 seconds, tell the user and stop.
5. Run the E2E tests
The Cloudflare Worker and MCP Inspector are started automatically by the test framework (via worker-setup.ts and shared helpers) — no manual setup needed.
Run the tests:
npm run test:e2e
If the user asked for a specific test, use:
npx playwright test --config tests/forms-hosted-e2e/e2e/playwright.config.ts -g "<test-name>"
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 · 93 lines · 78 tokens per session scan A 0b7a94b868a9
run-e2e is a skill published in the GitHub repository umbraco/Umbraco-MCP-Base (2 stars, last pushed yesterday), licensed MIT. It adds 78 tokens to every session and 869 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
test-warp-ui
Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…
pyats-dynamic-test
Generate and execute deterministic pyATS aetest validation scripts - interface state, OSPF neighbors, BGP paths, ping matrices, and custom compliance tests. Use when writing a network test, validating post-change state, running pass/fail checks, or building automated regression tests.
test-loop
Plan, generate, and heal an executable E2E test suite from approved acceptance criteria (web and mobile).
playwright-cli
Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or…