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 hmcts/agentic-plugins-marketplace --skill releasegit 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/release)<a href="https://agentmods.dev/skills/hmcts/agentic-plugins-marketplace/release"><img src="https://agentmods.dev/badge/skills/hmcts/agentic-plugins-marketplace/release/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/hmcts/agentic-plugins-marketplace/release"><img src="https://agentmods.dev/badge/skills/hmcts/agentic-plugins-marketplace/release.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.00048 | $0.01429 |
| Opus 5.5 | $0.00019 | $0.00572 |
| Sonnet 5.5 | $0.00010 | $0.00286 |
| Haiku 4.5 | $0.00005 | $0.00143 |
Grade A, and why
release 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 1mo 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 — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Release
Trigger
Invoke this skill when a user asks to:
- Create a new release
- Cut a release
- Tag and release the service
- Publish a new version
Invocation command: /release
Process
Step 1 — Get the last release tag
gh release list --limit 1 --json tagName,publishedAt,name
Extract:
tagName— current version (e.g.v1.2.4)publishedAt— ISO timestamp used to filter PRs
Tell the user: "Last release: <tagName> published on <date>."
Step 2 — Compute the next version
Default: increment the patch number.
| Current | Next (default) |
|---|---|
v1.2.4 |
v1.2.5 |
v2.0.0 |
v2.0.1 |
Override only if the user explicitly states:
minor→v1.2.4→v1.3.0major→v1.2.4→v2.0.0
Step 3 — Collect PRs merged since last release
gh pr list --state merged --limit 50 \
--json number,title,mergedAt,author,body \
--jq '.[] | select(.mergedAt > "<publishedAt>") | {number: .number, title: .title, author: .author.login, body: .body}'
Step 4 — Filter and categorise
Exclude entirely — do not mention in release notes:
- Author is
app/dependabotorapp/renovate - Title starts with
chore:,chore(deps):,docs:,ci: - Title matches pattern
bump <X> from <Y> to <Z> - PR configures or migrates dependency management tooling (e.g. Renovate → Dependabot, auto-merge workflow setup)
Categorise what remains:
| Category | Title signals |
|---|---|
| Bug Fixes | fix:, bugfix:, AMP-NNN bugfix: |
| New Features | feat:, feature:, AMP-NNN Add |
| Improvements | perf:, refactor:, chore(AMP- with JIRA ticket, Decommission, Switch, Replace |
| Other Changes | Anything else functional |
Step 5 — Generate release notes
For each included PR:
- Read the
## What changedsection from the PR body - Read the
## Why it's neededsection from the PR body - Write a plain-English summary of what the change does and why it matters — one short paragraph per PR
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.
- 1mo ago First seen · 177 lines · 48 tokens per session scan A e77f57f9a9bf
release is a skill published in the GitHub repository hmcts/agentic-plugins-marketplace (4 stars, last pushed today), licensed MIT. It adds 48 tokens to every session and 1,429 once invoked, about $0.0002 per session on Opus 5.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
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
release
Fully automate a release with version-bump and childhood.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.
updater_guide
Guidance for checking for and installing Row-Bot updates.