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 skills/hmcts/agentic-plugins-marketplace/cpp-test-authoringnpx skills add hmcts/agentic-plugins-marketplace --skill cpp-test-authoringgit 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/cpp-test-authoring)<a href="https://agentmods.dev/skills/hmcts/agentic-plugins-marketplace/cpp-test-authoring"><img src="https://agentmods.dev/badge/skills/hmcts/agentic-plugins-marketplace/cpp-test-authoring.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.00077 | $0.02137 |
| Opus 5 | $0.00039 | $0.01069 |
| Sonnet 5 | $0.00015 | $0.00427 |
| Haiku 4.5 | $0.00008 | $0.00214 |
Grade A, and why
cpp-test-authoring 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 3d 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.
CPP Test Authoring
Guides contributors through the conventions of the two HMCTS Crime Common Platform test repositories so new tests slot into existing patterns instead of forking them.
Repos covered:
cpp-ui-e2e-serenity— UI end-to-end (Serenity BDD 4.x + Cucumber 6 + Selenium, Java 17, Maven)cpp-apitests— API integration tests (JUnit 5 + REST Assured, Java 17, Maven)
When to Use
- User asks to add or extend a UI E2E test, Cucumber feature, step definition, or page object
- User asks to add or extend an API integration test (
*IT.java) - User asks "how do I add a test for X" while inside either repo
- Reviewing whether a proposed test follows the established pattern (defer the actual PR review to
review-pr)
When NOT to Use
- Authoring unit tests inside a runtime service (
cpp-context-*,cpp-mbd-*) — that's part of the service's own conventions - Writing or modifying Spring Boot service code — see
springboot-service-from-template - Pipeline failures — defer to
pipeline-debug - WCAG audits — defer to
accessibility-check
Prerequisites
Before writing test code:
- Story has acceptance criteria — apply
write-acceptance-criteriaif missing - For UI scenarios, the Gherkin draft exists — apply
generate-bdd-specsif missing - Jira ticket is linked (hard rule from
claude/CLAUDE.md) - No PII, case data, or court reference numbers in any planned fixture, feature, or assertion (hard rule)
Step 1 — Identify the Repo and Test Layer
| Repo | Layer | Marker files |
|---|---|---|
cpp-ui-e2e-serenity |
UI E2E | serenity.properties, azure-pipelines-dev01_*.yml, src/test/resources/features/ |
cpp-apitests |
API integration | apitests-pipeline.yaml, api-integration-test/ module, *IT.java suffixed tests |
If neither marker is present, stop — you're in the wrong repo.
Step 2 — UI E2E: Authoring a Serenity / Cucumber Test
Directory map
cpp-ui-e2e-serenity/
├── src/test/java/com/
│ ├── pageobjects/ # One class per page/section; holds locators + interactions
│ ├── stepdefinitions/ # Cucumber glue; extends the relevant page object
│ └── runner/ # TestRunner.java, RetryTestRunner.java
├── src/test/resources/
│ ├── features/<domain>/ # *.feature files (Gherkin)
│ ├── locators/custom-locators.json
│ └── testdata/<domain>/
└── serenity.properties
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.
- 3d ago First seen · 156 lines · 77 tokens per session scan A accbd6941c46
cpp-test-authoring is a skill published in the GitHub repository hmcts/agentic-plugins-marketplace (3 stars, last pushed 8d ago), licensed MIT. It adds 77 tokens to every session and 2,137 once invoked, about $0.0004 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
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
cli-e2e-testcase-writer
Use when adding or updating Go CLI E2E coverage for one tests/clie2e/{domain} domain of the compiled lark-cli, especially when the work requires live --help or schema exploration, scenario-based clie2e.RunCmd workflows, and per-domain coverage.md maintenance.
docs-build
Build, preview, and validate the Uno documentation website (DocFX) locally — surface real content errors vs expected noise, drive rendered pages with Playwright, and validate external-doc commit bumps in importexternaldocs.ps1 before a PR. Use when working under doc/, editing articles/ markdown, bumping an external…
verify
Exercise the real app/API/CLI and collect observable evidence; tests alone do not count as end-to-end verification.
harness-test-writer
Add regression test cases to the Bifrost provider harness (the Postman collection run via make run-provider-harness-test) based on a merged PR or a GitHub issue. Fetches the PR/issue, traces the affected wire path in the codebase, checks existing harness coverage, designs cases following harness conventions, inserts…
cli-e2e
Write, modify, or debug Docker-based Composio CLI end-to-end tests under ts/e2e-tests/cli, including binary invocation, fixture isolation, output assertions, and package manifests. Use for CLI E2E test suites only; use cli-command for CLI source implementation.