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 wire-service-deploymentgit 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/wire-service-deployment)<a href="https://agentmods.dev/skills/hmcts/agentic-plugins-marketplace/wire-service-deployment"><img src="https://agentmods.dev/badge/skills/hmcts/agentic-plugins-marketplace/wire-service-deployment/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/wire-service-deployment"><img src="https://agentmods.dev/badge/skills/hmcts/agentic-plugins-marketplace/wire-service-deployment.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.00124 | $0.03563 |
| Opus 5 | $0.00062 | $0.01782 |
| Sonnet 5 | $0.00025 | $0.00713 |
| Haiku 4.5 | $0.00012 | $0.00356 |
Grade A, and why
wire-service-deployment 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 9d 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 — 399 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Wire Service Deployment
When to invoke
Invoke once per service repo, after both of these external prerequisites are complete:
- Azure provisioning done — the
devGitHub environment exists on the repo and hasDEPLOYMENT_APP_IDandDEPLOYMENT_APP_PRIVATE_KEYsecrets configured. - Service registered in
cp-vp-aks-deploy— an entry for this service exists inhmcts/cp-vp-aks-deployundervp-config/services_values.yml.
If either prerequisite is missing, stop here and tell the user what is outstanding. Do not proceed until both are in place.
Invocation command: /wire-service-deployment
Step 1 — Identify the service repo
Confirm you are in the root of a service-cp-* repo (or that the user has named one).
Derive the service name:
REPO_NAME=$(gh repo view --json name -q '.name')
echo "Service repo: $REPO_NAME"
Step 2 — Idempotency check
Check whether the deployment jobs are already wired:
grep -q "deploy-dev:" .github/workflows/ci-build-publish.yml && echo "ALREADY_WIRED" || echo "NEEDS_WIRING"
If ALREADY_WIRED, tell the user: "Deployment jobs are already present in
ci-build-publish.yml. Nothing to do." and exit the skill.
Step 3 — Verify GitHub environment secrets
Check that the DEPLOYMENT_APP_ID and DEPLOYMENT_APP_PRIVATE_KEY secrets exist in the
dev environment. These are required by hmcts/action-ado-deploy@v1.
gh secret list --env dev 2>/dev/null | grep -E "DEPLOYMENT_APP_ID|DEPLOYMENT_APP_PRIVATE_KEY"
If either secret is missing, stop and tell the user:
"Prerequisites not met. The
devenvironment on this repo is missing one or both deployment secrets (DEPLOYMENT_APP_ID,DEPLOYMENT_APP_PRIVATE_KEY). Ask a platform engineer to configure these before running this skill."
Step 4 — Verify service registration in cp-vp-aks-deploy
Check that the service has an entry in the GitOps values file:
gh api "repos/hmcts/cp-vp-aks-deploy/contents/vp-config/services_values.yml" \
--jq '.content' | base64 -d | grep -q "$REPO_NAME" \
&& echo "REGISTERED" || echo "NOT_REGISTERED"
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.
- 9d ago First seen · 399 lines · 124 tokens per session scan A 4fe0bd494dea
wire-service-deployment is a skill published in the GitHub repository hmcts/agentic-plugins-marketplace (3 stars, last pushed yesterday), licensed MIT. It adds 124 tokens to every session and 3,563 once invoked, about $0.0006 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
import-prom-rule
Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.
webhook-management
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.