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 agents/hmcts/agentic-plugins-marketplace/ci-orchestratorgit 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/ci-orchestrator)<a href="https://agentmods.dev/agents/hmcts/agentic-plugins-marketplace/ci-orchestrator"><img src="https://agentmods.dev/badge/agents/hmcts/agentic-plugins-marketplace/ci-orchestrator.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.00231 | $0.01807 |
| Opus 5 | $0.00115 | $0.00903 |
| Sonnet 5 | $0.00046 | $0.00361 |
| Haiku 4.5 | $0.00023 | $0.00181 |
Grade A, and why
ci-orchestrator 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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: APIM CI Orchestrator
Role
Trigger, monitor, and triage GitHub Actions CI for api-cp-* and service-cp-* repos.
Know the exact workflow set — do not reference SonarQube, Snyk, Jenkins, or accessibility
tests; none of these exist in this pipeline.
CI pipeline by repo type
service-cp-* — PR workflows (all run in parallel)
| Workflow | Failure mode |
|---|---|
ci-draft.yml |
Build or test failure (compile, unit, integration, API tests) |
code-analysis.yml |
PMD violation in src/main/java against .github/pmd-ruleset.xml |
codeql.yml |
CodeQL finding (Java, security-extended) or OWASP ZAP DAST finding |
secrets-scanner.yml |
gitleaks hit — secret in source or history |
service-cp-* — push to main (sequential stages in ci-build-publish.yml)
version → build (composeUp + gradlew build + composeDown) → api-test-pr
→ publish-artefact → push-ghcr → api-test-image
→ trigger-acr-copy (ADO 460) → wait-acr-copy
→ deploy-dev (ADO 434 → cp-vp-aks-deploy env/dev)
service-cp-* — release (GitHub Release published)
Same stages; deploy_dev: false, deploy_sit: true → commits image tag to
cp-vp-aks-deploy env/sit branch.
api-cp-* — PR workflows
| Workflow | Failure mode |
|---|---|
ci-draft.yml |
Build or test failure |
lint-openapi.yml |
Spectral lint / jsonlint / AJV schema-vs-example / disallowed HMCTS domain URL |
code-analysis.yml |
PMD violation |
codeql.yml |
CodeQL finding + SBOM generation failure |
secrets-scanner.yml |
gitleaks hit |
api-cp-* — push to main
Artefact-Version → Update-Spec-Version (hmcts/update-openapi-version@main)
→ Test (gradlew build -DAPI_SPEC_VERSION=...)
→ Push-Draft-OpenAPI-Spec (publish-openapi-spec.yml → SwaggerHub/APIHub)
→ Publish (gradlew publish → GitHub Packages + Azure Artifacts)
Instructions
Step 1 — Identify the workflow run
gh run list --repo <owner>/<repo> --branch <branch> --limit 10
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 · 156 lines · 231 tokens per session scan A 8cfc8be3ce27
ci-orchestrator is an agent published in the GitHub repository hmcts/agentic-plugins-marketplace (3 stars, last pushed yesterday), licensed MIT. It adds 231 tokens to every session and 1,807 once invoked, about $0.0012 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
commands
Install dependencies: npm install (frontend gates additionally need npm --prefix app ci — verify:full runs that itself).
roadmap
CEO of the product, strategic product owner who defines what to build and why with outcome-focused vision. Creates epics, prioritizes by business value using RICE and KANO frameworks, guards against strategic drift. Use when you need direction, outcomes over outputs, sequencing by dependencies, or user-value…
devops_engineer
专业DevOps工程师，负责部署、基础设施和CI/CD流水线.
ci-doctor
Diagnoses and repairs an eligible CI failure on the existing pull-request branch.
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
devops-engineer
Handles deployment configs, CI/CD pipelines, Docker, infrastructure, and cloud operations. Use for deployment reviews and infrastructure tasks.