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 commands/consensys/ask-o11y-plugin/maintain-test-coveragegit clone --depth 1 https://github.com/Consensys/ask-o11y-pluginWrote 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/commands/consensys/ask-o11y-plugin/maintain-test-coverage)<a href="https://agentmods.dev/commands/consensys/ask-o11y-plugin/maintain-test-coverage"><img src="https://agentmods.dev/badge/commands/consensys/ask-o11y-plugin/maintain-test-coverage.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.00000 | $0.00700 |
| Opus 5 | $0.00000 | $0.00350 |
| Sonnet 5 | $0.00000 | $0.00140 |
| Haiku 4.5 | $0.00000 | $0.00070 |
Grade A, and why
maintain-test-coverage 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 5d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Maintain Test Coverage
Overview
Achieve 65% line coverage through a combination of E2E tests and unit tests. Coverage reports are merged from both test types into a single unified report.
Commands
| Command | Description |
|---|---|
npm run coverage |
Run all tests and generate combined coverage report |
npm run coverage:e2e |
Run only E2E tests with coverage (standalone) |
npm run coverage:unit |
Run only unit tests with coverage |
npm run coverage:merge |
Merge existing coverage outputs |
Workflow
-
Run Combined Coverage
npm run coverageThis command:
- Cleans previous coverage data
- Runs unit tests with coverage
- Builds frontend with instrumentation
- Runs E2E tests with coverage
- Merges all coverage into
coverage-combined/
-
Review Coverage Report
- Check terminal output for line percentage
- Open
coverage-combined/index.htmlfor detailed report - If line coverage is below 65%, continue to step 3
-
Add Tests for Uncovered Code
- E2E tests: Add to
tests/directory using Playwright - Unit tests: Add to
src/**/__tests__/orsrc/**/*.test.ts - Re-run
npm run coverageto verify improvement
- E2E tests: Add to
-
Iterate Until 65% Line Coverage
Test Strategy
E2E Tests (Playwright) - tests/
Best for:
- React components with user interactions
- Page navigation and routing
- Form submissions and validations
- Visual state changes
Unit Tests (Jest) - src/**/__tests__/
Best for:
- Pure utility functions
- Data transformation logic
- Parsers and validators
- Service classes with mockable dependencies
Priority Areas
E2E (UI Components)
- Chat Input & Submission
- Session Management
- AppConfig settings
- System Prompt Configuration
Unit Tests (Services)
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.
- 5d ago First seen · 96 lines · 0 tokens per session scan A 335cf0b4bcbd
maintain-test-coverage is a command published in the GitHub repository Consensys/ask-o11y-plugin (40 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 700 tokens. 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-30.
Other commands, from other repositories
test-suite
Run comprehensive test suite with coverage analysis.
gsd:add-tests
Generate tests for a completed phase based on UAT criteria and implementation.
testing
Comprehensive testing through distributed execution.
verify
You are invoking the verify skill - comprehensive verification following Boris Cherny's pattern.
test
Escrever e rodar testes (skill 05 — QA Engineer).
quality-check-command
This command performs comprehensive code quality checks. Use it before commits or when implementation is complete.