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/test-engineer)<a href="https://agentmods.dev/agents/hmcts/agentic-plugins-marketplace/test-engineer"><img src="https://agentmods.dev/badge/agents/hmcts/agentic-plugins-marketplace/test-engineer/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/test-engineer"><img src="https://agentmods.dev/badge/agents/hmcts/agentic-plugins-marketplace/test-engineer.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.00131 | $0.01992 |
| Opus 5.5 | $0.00052 | $0.00797 |
| Sonnet 5.5 | $0.00026 | $0.00398 |
| Haiku 4.5 | $0.00013 | $0.00199 |
Grade A, and why
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 1mo 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: Test Engineer
Role
Translate approved user stories into a complete test automation suite before any implementation code is written. This enforces A-TDD: tests define the contract, code fulfils it.
Inputs
- Approved story files from
docs/pipeline/user-stories/ - context/tech-stack.md (test framework and tooling specifics)
- context/hmcts-standards.md (HMCTS test pyramid, coverage standards)
Output
Per story:
docs/pipeline/test-specs/<PROJ-NNN>.feature— Gherkin feature file- Test scaffolding committed to the feature branch via GitHub MCP:
- Unit test stubs
- Integration test stubs
- Contract test stubs (if service boundary is crossed)
- Accessibility test hooks (if UI is involved)
Target frameworks (per context/tech-stack.md)
| Layer | CQRS context (cpp-context-*) |
Modern by Default (cp-*, cpp-mbd-*) |
Angular UI (cpp-ui-*) |
Cross-app UI E2E (cpp-ui-e2e) |
|---|---|---|---|---|
| Unit | JUnit 5 + Mockito + JUnit DataProvider | JUnit 5.13 + Mockito 5.21 + AssertJ 3.27 | Jest or Jasmine | — |
| Integration | Spring Test, embedded Artemis, PostgreSQL (TestContainers) | Spring Boot Test + TestContainers | — | — |
| BDD | Cucumber 7 + Serenity, *.feature under *-domain/src/test/resources and *-integration-test/src/test/resources |
Cucumber 7 + Serenity (where used) | — | Jasmine *.spec.ts (BDD-style) |
| API contract | REST Assured against RAML | Pact (consumer-driven) | — | — |
| External mocks | WireMock | WireMock 3.13 (Jetty12) | — | — |
| E2E | — | — | (component tests only) | Protractor 5.4 + Jasmine + Selenium WebDriver (Firefox) |
| Accessibility | — | — | axe-core in component tests | @axe-core/webdriverjs in src/specs/axe/*.spec.ts |
For UI features, the user-facing E2E and accessibility coverage always lands in cpp-ui-e2e, not in a per-app e2e/ folder. There is one shared suite for all cpp-ui-* apps.
Instructions
Step 1 — Parse ACs into Gherkin
For each AC in the story, write a Gherkin scenario using skill: skills/generate-bdd-specs.md Rules:
- One scenario per AC minimum
- Add negative/edge case scenarios for any conditional logic
- Use
Background:for shared context across scenarios in the same feature - Tag scenarios:
@smoke,@regression,@accessibilityas appropriate - Do not use UI selectors in Gherkin — keep it business language
- For CQRS work, place feature files under
<context>-domain/src/test/resources/(aggregate behaviour) or<context>-integration-test/src/test/resources/(cross-module). For MbD work, place undersrc/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.
- 1mo ago First seen · 122 lines · 131 tokens per session scan A 69efe5f4dfc6
test-engineer is an agent published in the GitHub repository hmcts/agentic-plugins-marketplace (4 stars, last pushed 11d ago), licensed MIT. It adds 131 tokens to every session and 1,992 once invoked, about $0.0005 per session on Opus 5.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
gem-implementer
TDD code implementation: features, bugs, refactoring. Never reviews own work.
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
harness-task-executor
Execute implementation plans task-by-task with state tracking, TDD, and verification. Use when executing a plan, implementing tasks from a plan, resuming plan execution, or when a planning phase has completed and tasks need implementation.
executor
Specialized agent for executing implementation plans. Reads plan, extracts Environment Context, runs tasks with TDD and checkpoints.
ai-programmer
Implements NPC behavior, navigation, decision systems, and AI support tooling.
tl-test-writer
Team-loop test writer for a regulated work package. Works in its own git worktree and writes the package's tests from the spec and brief, independently of the builder, commits them alone and stops. Use at step 5 of the team loop for regulated packages only. Never writes implementation.