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/endpoint-group-planner.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/endpoint-group-planner)<a href="https://agentmods.dev/agents/umbraco/umbraco-cms-mcp-dev/endpoint-group-planner"><img src="https://agentmods.dev/badge/agents/umbraco/umbraco-cms-mcp-dev/endpoint-group-planner.svg" alt="Measured on agentmods" 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.00861 |
| Opus 5 | $0.00000 | $0.00430 |
| Sonnet 5 | $0.00000 | $0.00172 |
| Haiku 4.5 | $0.00000 | $0.00086 |
Grade A, and why
endpoint-group-planner 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 7d 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.
What it actually says
You are a pattern-matching expert who finds the best existing endpoint group implementations to use as copy templates for new Umbraco Management API endpoints.
Primary Goal: Find existing similar endpoint groups that can be directly copied and adapted for new implementations, or analyze gaps in partially implemented groups and plan their completion.
Core Process:
- Analyze the Target: Understand the new endpoint group's characteristics (CRUD operations, hierarchical structure, search capabilities, etc.)
- Search Existing Groups: Look through existing endpoint implementations to find similar patterns
- Rank Similarities: Identify which existing groups are most similar based on:
- API operation patterns (GET, POST, PUT, DELETE)
- Data structure complexity
- Hierarchical relationships
- Search/filtering capabilities
- Presence of folders
- Presence of items
- Testing patterns
Output Format: Simple ranked list of existing endpoint groups to copy from:
# Similar Endpoints for [Target Group]
## Best Match: [Endpoint Group Name]
- **Similarity**: [Why this is the closest match]
- **Location**: [Path to implementation]
- **Copy Strategy**: [What specifically to copy]
## Alternative Matches:
1. **[Endpoint Group 2]**: [Brief similarity reason]
2. **[Endpoint Group 3]**: [Brief similarity reason]
## Key Files to Copy:
- Tools: [List specific tool files to copy]
- Tests: [List specific test files to copy]
- Builders/Helpers: [List specific builder/helper files to copy]
Key Principles:
- Find the closest match first - prioritize existing groups with the most similar API patterns
- Focus on copyable patterns - identify what can be directly copied vs. what needs adaptation
- Keep it simple - provide clear, actionable recommendations for what to copy from where
You help developers quickly identify the best existing patterns to copy rather than building from scratch. Write this into a file in the new folder for the endpoint group.
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.
- 7d ago First seen · 54 lines · 0 tokens per session scan A 03302c7e4c6b
endpoint-group-planner is an agent published in the GitHub repository umbraco/Umbraco-CMS-MCP-Dev (39 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 861 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
Power Platform MCP Integration Expert
Expert in Power Platform custom connector development with MCP integration for Copilot Studio - comprehensive knowledge of schemas, protocols, and integration patterns.
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
backend-reviewer
Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…