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 agentmods add skills/hmcts/agentic-plugins-marketplace/springboot-api-from-templatenpx skills add hmcts/agentic-plugins-marketplace --skill springboot-api-from-templategit 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/skills/hmcts/agentic-plugins-marketplace/springboot-api-from-template)<a href="https://agentmods.dev/skills/hmcts/agentic-plugins-marketplace/springboot-api-from-template"><img src="https://agentmods.dev/badge/skills/hmcts/agentic-plugins-marketplace/springboot-api-from-template.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 | $0.00065 | $0.03255 |
| Opus 5 | $0.00032 | $0.01628 |
| Sonnet 5 | $0.00013 | $0.00651 |
| Haiku 4.5 | $0.00006 | $0.00326 |
Grade A, and why
springboot-api-from-template 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 5d 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 — 300 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HMCTS API-Marketplace API from Template
This skill stands up a new OpenAPI specification repository from the HMCTS template. API spec repos are distinct from runtime services:
- api-cp-* repos contain the OpenAPI spec, validation tooling, generators, and publishing workflows. They produce the spec artefact consumed by services.
- service-cp-* repos contain the runtime Spring Boot implementation and
consume one or more api-cp-* artefacts. Use
springboot-service-from-templatefor those.
Do not mix runtime code into an api-cp-* repo.
API-first — why this skill runs before springboot-service-from-template
Every service-cp-* has a matching api-cp-*, and this skill produces that
API repo. It is intended to run before the service skill — ideally with
time in between to review the contract with consumers.
The split is deliberate:
- The contract has its own cadence of change, driven by consumer needs and cross-team agreement — not by the implementation team's sprint.
- Engineering teams naturally want to jump into code when they should still be designing the API. This separation makes jumping ahead awkward by design: the service cannot build without an API artefact to depend on.
- Collapsing API and service into one repo couples contract design to service delivery and produces whatever API the service happened to ship, not the API the consumers actually need.
Repo-pair naming convention shares the suffix so the link is obvious:
- API repo:
api-cp-[case-type]-{business-domain}-{entity} - Service repo:
service-cp-[case-type]-{business-domain}-{entity}
If a user jumps straight to springboot-service-from-template without an
API repo in place, redirect them here first.
Master source
GitHub: https://github.com/hmcts/api-hmcts-crime-template
Everything under build.gradle, gradle/, .github/workflows/, and the
validation tooling belongs to the template. This skill must not inline those
files.
Context to pull in
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.
- 5d ago First seen · 300 lines · 65 tokens per session scan A 7931ce45db7a
springboot-api-from-template is a skill published in the GitHub repository hmcts/agentic-plugins-marketplace (3 stars, last pushed 9d ago), licensed MIT. It adds 65 tokens to every session and 3,255 once invoked, about $0.0003 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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…