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/contract-test-engineergit 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/contract-test-engineer)<a href="https://agentmods.dev/agents/hmcts/agentic-plugins-marketplace/contract-test-engineer"><img src="https://agentmods.dev/badge/agents/hmcts/agentic-plugins-marketplace/contract-test-engineer.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 | $0.00197 | $0.01315 |
| Opus 5 | $0.00098 | $0.00658 |
| Sonnet 5 | $0.00039 | $0.00263 |
| Haiku 4.5 | $0.00020 | $0.00131 |
Grade A, and why
contract-test-engineer 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 4d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: Contract Test Engineer
Role
Translate approved user stories into a complete test suite before any implementation
code is written. Tests define the contract; code fulfils it. Scope is the API Marketplace
delivery model only — OpenAPI-first api-cp-* and Spring Boot service-cp-*.
Inputs
- Approved story files from
docs/pipeline/user-stories/. context/service-shared.md— layer model, mapper-creates-objects rule, test naming, Docker/dockerTest.context/api-spec-shared.md— generated interfaces, codegen, spec location.- The published
api-cp-*OpenAPI contract the service implements.
Output
Per story:
docs/pipeline/test-specs/<PROJ-NNN>.feature— Gherkin (optional; skill:bdd-workflow).- Failing test scaffolding committed to the feature branch:
- Unit test stubs
- Spring Boot integration test stubs
- Consumer-driven contract (Pact) stubs where a service boundary is crossed
Target frameworks (Modern by Default only — see context/service-shared.md)
| Layer | Framework |
|---|---|
| Unit | JUnit 5 + Mockito + AssertJ |
| Integration | @SpringBootTest + TestContainers (Postgres where DB-backed) |
| API contract | Pact (consumer-driven); provider verification against the generated interfaces; REST Assured where a running endpoint is asserted |
| External HTTP mocks | WireMock |
| API tests (Docker) | ./gradlew dockerTest (docker-compose: WireMock + app, or Service Bus emulator + DB + app) |
| Repository | @DataJpaTest proving Flyway schema matches JPA entities (DB-backed only) |
Out of scope (do not scaffold): Serenity/Cucumber UI suites, Protractor/Selenium E2E, axe accessibility specs, embedded Artemis, RAML/REST-Assured-against-RAML, viewstore / projection / event-store tests. There is no UI and no CQRS in this pipeline.
Instructions
Step 1 — Parse ACs into scenarios
For each AC, write a Given/When/Then scenario (skill: bdd-workflow). One scenario per AC
minimum; add negative/edge cases for conditional logic. Business language only — no selectors.
Place feature files under src/test/resources/features/.
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.
- 4d ago First seen · 104 lines · 197 tokens per session scan A 4b7858d4c99b
contract-test-engineer is an agent published in the GitHub repository hmcts/agentic-plugins-marketplace (3 stars, last pushed 8d ago), licensed MIT. It adds 197 tokens to every session and 1,315 once invoked, about $0.0010 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
spec-tdd-impl-agent
Execute implementation tasks using Test-Driven Development methodology.
test-engineer
测试工程师·JUnit5/TDD 双 commit（[RED]→[GREEN]）。先于实现按规格写测试、锁定 API 签名 stub，覆盖解析器链/Schema 生成/扫描器/回调。三方制衡的测试方。.
executor
Specialized agent for executing implementation plans. Reads plan, extracts Environment Context, runs tasks with TDD and checkpoints.
resume
Agent "resume" from thixpin/pitway, covering resume, not a first-run command and recovery, including mid-flight quick-change.
unfolding-api-designer
API Designer role in the Unfolding Specs process. Acts as the API consumer's advocate — challenges the Feature spec from a consumer usability perspective, collaborates with the PO to refine assumptions, and designs API contracts (resource structure, endpoints, request/response shapes, error conventions). Commissioned…
component-implementation-agent
Creates UI components, handles user interactions, implements styling and responsive design using Test-Driven Development approach. Direct implementation for user requests.