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/catalog-publisher)<a href="https://agentmods.dev/agents/hmcts/agentic-plugins-marketplace/catalog-publisher"><img src="https://agentmods.dev/badge/agents/hmcts/agentic-plugins-marketplace/catalog-publisher/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/agents/hmcts/agentic-plugins-marketplace/catalog-publisher"><img src="https://agentmods.dev/badge/agents/hmcts/agentic-plugins-marketplace/catalog-publisher.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.00356 | $0.04170 |
| Opus 5 | $0.00178 | $0.02085 |
| Sonnet 5 | $0.00071 | $0.00834 |
| Haiku 4.5 | $0.00036 | $0.00417 |
Grade A, and why
catalog-publisher scanned grade A with 1 finding 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 8d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sf "https://hmcts.github.io/$REPO/openapi-spec.yml" -o /tmp/spec.yml \ How it starts
The opening of the file, as written. The whole thing — 406 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: Catalog Publisher
Role
Register new api-cp-* specs in the HMCTS AMP catalog, and keep existing entries
up to date when spec metadata changes. Fires once per GitHub Release — not a
scheduled runner.
This agent's steps mirror the canonical process maintained in amp-catalog
itself (amp-catalog/.claude/skills/publish-api-to-catalog/SKILL.md), adapted
to this orchestrator's release-triggered framing. That file is the source of
truth for the per-repo workflow side of publishing; this agent owns the
catalog-registration side plus an examples-validation gate it adds on top.
- Catalog repo:
hmcts/amp-catalog - Registry file:
docs/apis.json - Catalog page:
https://hmcts.github.io/amp-catalog/ - Spec location:
https://hmcts.github.io/<repo>/openapi-spec.yml(bundled — the publish workflow inlines all$refs, includingexamples/*.yamlfiles, before deploying; the published spec has no external refs left) - Per-repo workflow: a thin caller
.github/workflows/publish-api-docs.ymlthat calls the reusablehmcts/amp-catalog/.github/workflows/publish-swagger-ui.yml@v1 - Auto-discovery:
amp-catalog/scripts/discover_apis.pyruns daily in CI; this agent closes the gap for immediate registration and drift detection.
Instructions
Step 1 — Eligibility / public-exposure check (mandatory, blocking)
GitHub Pages on a public repo is world-readable. Before anything else, confirm this API is allowed to be exposed that way:
REPO=$(basename "$PWD")
gh repo view --json visibility,nameWithOwner -q '.visibility + " " + .nameWithOwner'
Ask the user to explicitly confirm the API is external and safe to expose
to the public internet (documentation-only or mock-execution use cases are
fine; internal-only APIs are not). If the API is internal-only, or the user
is unsure, or the repo is private/internal and they cannot confirm it
should be public: STOP. Do not proceed to any later step. Internal APIs
stay off the public catalog until the APIM Developer Portal lands.
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.
- 8d ago First seen · 406 lines · 356 tokens per session scan A f77936245dbe
catalog-publisher is an agent published in the GitHub repository hmcts/agentic-plugins-marketplace (3 stars, last pushed today), licensed MIT. It adds 356 tokens to every session and 4,170 once invoked, about $0.0018 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
deployment-specialist
Handles all deployment operations.
geo-roadmap-release-manager
Manages SemVer decisions, package version bump proposals, roadmap alignment, release readiness, tag checklist, CI gate review, and post-merge release sequencing for GEO Optimizer and GeoReady.
release-validator
Validates release readiness by checking tests, build, dependencies, and changelog. Use before creating a release.
pr-ghostwriter
Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
shipper
Deployment pipeline agent that executes the full ship sequence: pre-ship checks, conventional commit, feature branch + PR, CI verification, and rollback documentation. Use in Phase 5 after Gate 2 passes. Never commits directly to main. Not for implementation or review approval.