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/plugins/hmcts/agentic-plugins-marketplace/hmcts-sdlc-orchestrator)<a href="https://agentmods.dev/plugins/hmcts/agentic-plugins-marketplace/hmcts-sdlc-orchestrator"><img src="https://agentmods.dev/badge/plugins/hmcts/agentic-plugins-marketplace/hmcts-sdlc-orchestrator.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
hmcts-sdlc-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 7d 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.
What it actually says
{
"name": "hmcts-sdlc-orchestrator",
"version": "1.0.0",
"description": "HMCTS SDLC pipeline orchestrator for Crime Common Platform — bundles the 8-stage pipeline sub-agents, HMCTS-specific skills (Spring Boot service/API templates, CPP test authoring), context docs (tech-stack, HMCTS standards, Azure cloud-native, logging, Azure SDK), guard hooks (PII, secrets, bash, paths), and the opsx commands.",
"author": {
"name": "HMCTS Crime Common Platform"
},
"license": "MIT",
"keywords": [
"hmcts",
"cpp",
"sdlc",
"orchestrator",
"spring-boot",
"azure",
"agents",
"pipeline"
]
}
What it installs
The manifest is a name and a version. 10 skills, 9 agents travel with it, and installing the plugin installs all of them — 1,907 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill cpp-test-authoring A 77 tokens
- Skill pipeline-debug A 36 tokens
- Skill review-pr A 42 tokens
- Skill api-contract-check A 36 tokens
- Skill context-scaffold A 44 tokens
- Skill context-service-guide A 53 tokens
- Skill terraform-validate A 29 tokens
- Skill dependency-audit A 31 tokens
- Skill architecture-design A 83 tokens
- Skill export-design-artifact A 274 tokens
- Agent test-analyzer A 138 tokens
- Agent architecture-designer A 164 tokens
- Agent doc-generator A 129 tokens
- Agent helm-config-validator A 119 tokens
- Agent migration-reviewer A 120 tokens
- Agent rbac-auditor A 131 tokens
- Agent event-flow-mapper A 118 tokens
- Agent research A 152 tokens
- Agent test-engineer A 131 tokens
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.
- 7d ago First seen · 20 lines scan A 213d54351ac8
hmcts-sdlc-orchestrator is a plugin published in the GitHub repository hmcts/agentic-plugins-marketplace (3 stars, last pushed 2d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
api-tester
Use this agent for comprehensive API testing including performance testing, load testing, and contract testing. This agent specializes in ensuring APIs are robust, performant, and meet specifications before deployment. Examples:\n\n \nContext: Testing API performance under load.
api-contract-testing
Verifies API contracts between services using consumer-driven contracts, schema validation, and tools like Pact. Use when testing microservices communication, preventing breaking changes, or validating OpenAPI specifications.
load-tester
Load and stress testing for APIs and web services.
rails-toolkit
Complete Rails development workflow with TDD, security reviews, and Linear integration.
api-integration-helper
Connector - Production-ready API integration specialist. Orchestrates 10 agents to generate typed clients, auth flows, error handling, rate limiting, and mock servers from OpenAPI/GraphQL specs. Delivers enterprise-grade API integrations, not basic fetch wrappers.
vitest-auto-spy
Typed test spies from a class or a type on Vitest, bun:test and node:test — the skill teaches an agent the API, the anti-patterns, the error→fix table and the codemod that migrates a suite off jest-auto-spies or jasmine-auto-spies.