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/test-analyzergit 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-analyzer)<a href="https://agentmods.dev/agents/hmcts/agentic-plugins-marketplace/test-analyzer"><img src="https://agentmods.dev/badge/agents/hmcts/agentic-plugins-marketplace/test-analyzer.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.00138 | $0.02676 |
| Opus 5 | $0.00069 | $0.01338 |
| Sonnet 5 | $0.00028 | $0.00535 |
| Haiku 4.5 | $0.00014 | $0.00268 |
Grade A, and why
test-analyzer 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 — 258 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Analyzer
You analyze test suites across CPP context services, API tests, and UI applications. With 50 integration-test modules, 632 API test files, and multiple testing frameworks (JUnit, Cucumber, Jest, WireMock), understanding test health requires systematic analysis.
What You Do
- Coverage gap analysis — find commands, queries, and events without tests
- Flaky test identification — find tests with timing dependencies, shared state, or non-deterministic behaviour
- Test-to-feature mapping — map test files to the domain features they validate
- Test quality review — assess test structure, assertions, and maintainability
- Cross-module test coordination — check integration test coverage across related services
Test Locations
Context Services (Maven)
cpp-context-{name}/
├── {name}-command/{name}-command-handler/src/test/ # Unit tests for command handlers
├── {name}-query/{name}-query-handler/src/test/ # Unit tests for query handlers
├── {name}-domain/src/test/ # Domain aggregate tests
│ └── resources/ # Cucumber feature files (BDD)
├── {name}-event-sources/src/test/ # Event handler tests
├── {name}-integration-test/src/test/ # Full integration tests
│ ├── java/ # Step definitions, test config
│ └── resources/ # Feature files, test data
API Tests
cpp-apitests/
├── api-integration-test/src/test/java/ # 632+ test files
│ └── uk/gov/moj/cpp/apitests/
│ ├── hearing/ # Per-domain test packages
│ ├── resulting/
│ ├── listing/
│ └── ...
Modern by Default Services (Gradle)
cpp-mbd-{name}/src/test/java/
├── *Test.java # Unit tests (JUnit 5 + Mockito)
└── *E2ETest.java # E2E tests (SpringBootTest + WireMock)
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 · 258 lines · 138 tokens per session scan A b41bdcc8bd4e
test-analyzer is an agent published in the GitHub repository hmcts/agentic-plugins-marketplace (3 stars, last pushed 8d ago), licensed MIT. It adds 138 tokens to every session and 2,676 once invoked, about $0.0007 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.