Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add umbraco/Umbraco-MCP-Base/plugin install umbraco-mcp-skillsWrote 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/discuss-mcp)<a href="https://agentmods.dev/skills/umbraco/umbraco-mcp-base/discuss-mcp"><img src="https://agentmods.dev/badge/skills/umbraco/umbraco-mcp-base/discuss-mcp/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/discuss-mcp"><img src="https://agentmods.dev/badge/skills/umbraco/umbraco-mcp-base/discuss-mcp.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.00030 | $0.01039 |
| Opus 5 | $0.00015 | $0.00519 |
| Sonnet 5 | $0.00006 | $0.00208 |
| Haiku 4.5 | $0.00003 | $0.00104 |
Grade A, and why
discuss-mcp 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Discuss MCP
Advisory skill for reflecting on and improving an MCP server. Unlike builder skills (/build-tools, /build-evals) that execute generation workflows, this skill is conversational — it helps developers understand what to improve, why, and how.
When to Use
Use this skill when the developer asks:
- "How can I improve my MCP server?"
- "Why are my evals slow/expensive/failing?"
- "Should I add composite tools or proxy tools?"
- "What tools am I missing?"
- "What should I build next?"
- "Are my tools well-designed?"
- "How do I reduce eval cost/turns?"
Improvement Paths
Route to the appropriate sub-file based on what the developer wants to discuss:
1. Trace Optimization — "My evals are slow/expensive/failing"
The developer wants to analyze eval performance and iteratively improve tools based on trace data.
Read: trace-optimization.md
Signals: mentions evals, traces, cost, turns, tokens, performance, "why does the LLM struggle", repeated tool calls, wrong tool selection.
2. Chained Tool Design — "Should I add composite/proxy tools?"
The developer wants to discuss adding tools that delegate to other MCP servers — whether to proxy or create composites.
Read: chained-tools.md
Signals: mentions chaining, proxy, composite, multi-server, delegation, orchestration, combining data from multiple sources.
3. Behavioral Analysis — "What should I build next?"
The developer wants a holistic review of their MCP: coverage gaps, organizational quality, prioritization of next steps.
Read: behavioral-analysis.md
Signals: mentions coverage, gaps, what's missing, next steps, priorities, tool organization, modes, slices, "are my tools well-designed".
Conversational Guidelines
When advising on MCP improvements, follow these principles:
- Ask before recommending. Understand the developer's goals before suggesting changes. "What workflows are you trying to support?" is more useful than jumping to solutions.
What ships with it
5 files 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.
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 · 72 lines · 30 tokens per session scan A 58ef15c5a3d6
discuss-mcp is a skill published in the GitHub repository umbraco/Umbraco-MCP-Base (2 stars, last pushed yesterday), licensed MIT. It adds 30 tokens to every session and 1,039 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…