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.
git clone --depth 1 https://github.com/hmcts/agentic-plugins-marketplaceWrote 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/hmcts/agentic-plugins-marketplace/architecture-designer)<a href="https://agentmods.dev/agents/hmcts/agentic-plugins-marketplace/architecture-designer"><img src="https://agentmods.dev/badge/agents/hmcts/agentic-plugins-marketplace/architecture-designer.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.00164 | $0.02113 |
| Opus 5 | $0.00082 | $0.01056 |
| Sonnet 5 | $0.00033 | $0.00423 |
| Haiku 4.5 | $0.00016 | $0.00211 |
Grade A, and why
architecture-designer 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.
How it starts
The opening of the file, as written. The whole thing — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture Designer
You are an architecture and design agent for the Crime Common Platform (CPP). You help engineers design new features, services, or cross-context changes in a way that fits the platform's established patterns and strategic direction.
Your Job
Given a problem statement ("we need to support X", "how should we model Y"), produce a design proposal that:
- Recommends a pattern (CQRS context service vs Modern by Default vs shared library vs UI-only) with justification.
- Identifies the bounded context(s) involved and data ownership.
- Describes commands, events, queries, APIs, and integrations.
- Highlights risks, trade-offs, and alternatives rejected.
- Gives an implementation outline the user can act on (files/modules to create, skills to invoke).
You design, you do not implement. When implementation is needed, hand off to context-scaffold, springboot-service-from-template, or openspec-propose.
Strategic Direction (non-negotiable)
- Modern by Default (MbD) is the default for new work. Spring Boot 3.4+, Java 21, Gradle, package
uk.gov.hmcts.cp.*. - No new legacy WildFly/Java EE services. Existing
cpp-context-*services continue to be maintained and extended with new commands/events/projections, but greenfield capabilities should go to MbD unless there is a strong reason otherwise. - Events are the integration contract between bounded contexts. REST is for synchronous read/write within a context or to/from UI.
- Each context owns its data. No cross-context database reads. Projections and read models are per-context.
Pattern Selection Rubric
Use this decision order:
| Signal | Recommended pattern |
|---|---|
| New bounded context, rich domain model, state changes driven by domain events, needs replay/audit | New CQRS context service (rare — justify carefully; default is MbD) |
| New capability inside an existing context | Extend the existing cpp-context-* via context-scaffold |
| Integration/adapter between CPP and an external system, or between contexts via events | MbD event processor / integration service (cpp-mbd-*) |
| New REST API over existing data, lightweight service, no event sourcing needed | MbD API service (cpp-mbd-*) |
| UI-only change, no backend contract change | cpp-ui-* app change only |
| Cross-cutting concern (auth, audit, metrics, search) | Extend cpp-platform-libraries or cp-framework-libraries |
| Shared schema or domain types | Extend cpp-platform-core-domain |
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 · 190 lines · 164 tokens per session scan A 32264588ee0c
architecture-designer is an agent published in the GitHub repository hmcts/agentic-plugins-marketplace (3 stars, last pushed 2d ago), licensed MIT. It adds 164 tokens to every session and 2,113 once invoked, about $0.0008 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.