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/sifxprime/kodelyth-eccWrote 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/sifxprime/kodelyth-ecc/test-coverage)<a href="https://agentmods.dev/commands/sifxprime/kodelyth-ecc/test-coverage"><img src="https://agentmods.dev/badge/commands/sifxprime/kodelyth-ecc/test-coverage/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/commands/sifxprime/kodelyth-ecc/test-coverage"><img src="https://agentmods.dev/badge/commands/sifxprime/kodelyth-ecc/test-coverage.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.00011 | $0.00631 |
| Opus 5.5 | $0.00004 | $0.00252 |
| Sonnet 5.5 | $0.00002 | $0.00126 |
| Haiku 4.5 | $0.00001 | $0.00063 |
Grade A, and why
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 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.
Copies of this mod
3 near-identical copies found in the catalogue:
- ccc-test-coverage — 97% identical, 105 lines differ
- test-coverage — 94% identical, 6 lines differ
- test-coverage — 94% identical, 6 lines differ
How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Coverage
Analyze test coverage, identify gaps, and generate missing tests to reach 80%+ coverage.
Step 1: Detect Test Framework
| Indicator | Coverage Command |
|---|---|
jest.config.* or package.json jest |
npx jest --coverage --coverageReporters=json-summary |
vitest.config.* |
npx vitest run --coverage |
pytest.ini / pyproject.toml pytest |
pytest --cov=src --cov-report=json |
Cargo.toml |
cargo llvm-cov --json |
pom.xml with JaCoCo |
mvn test jacoco:report |
go.mod |
go test -coverprofile=coverage.out ./... |
Step 2: Analyze Coverage Report
- Run the coverage command
- Parse the output (JSON summary or terminal output)
- List files below 80% coverage, sorted worst-first
- For each under-covered file, identify:
- Untested functions or methods
- Missing branch coverage (if/else, switch, error paths)
- Dead code that inflates the denominator
Step 3: Generate Missing Tests
For each under-covered file, generate tests following this priority:
- Happy path — Core functionality with valid inputs
- Error handling — Invalid inputs, missing data, network failures
- Edge cases — Empty arrays, null/undefined, boundary values (0, -1, MAX_INT)
- Branch coverage — Each if/else, switch case, ternary
Test Generation Rules
- Place tests adjacent to source:
foo.ts→foo.test.ts(or project convention) - Use existing test patterns from the project (import style, assertion library, mocking approach)
- Mock external dependencies (database, APIs, file system)
- Each test should be independent — no shared mutable state between tests
- Name tests descriptively:
test_create_user_with_duplicate_email_returns_409
Step 4: Verify
- Run the full test suite — all tests must pass
- Re-run coverage — verify improvement
- If still below 80%, repeat Step 3 for remaining gaps
Step 5: Report
Show before/after comparison:
Coverage Report
──────────────────────────────
File Before After
src/services/auth.ts 45% 88%
src/utils/validation.ts 32% 82%
──────────────────────────────
Overall: 67% 84% PASS:
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 · 74 lines · 11 tokens per session scan A dc7c4ff1532d
test-coverage is a command published in the GitHub repository sifxprime/kodelyth-ecc (11 stars, last pushed 12d ago), licensed MIT. It adds 11 tokens to every session and 631 once invoked, about $0.0000 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-09-03.
Other commands, from other repositories
maintainer-review-test-coverage
Review the PR for test coverage — does new behavior have tests, are critical paths exercised, do existing tests still cover what they should (Pi-tuned).
discover-checks
Find the project's own checks and declare them. You do not run the gate: a script runs exactly what you declare, for as long as it takes, and records every exit status. Your declaration is the whole of what gets validated, so it must be the project's gate and nothing else.
record
Record a browser walkthrough of a URL using Antigravity (agy). Generates .webm video, screenshots, and a report. Auto-converts to MP4 if ffmpeg is available.
constraints
A command for defining a project's quality standards through a short interview and a written CONSTRAINTS.md file. It records checks, thresholds, exceptions, and commands for enforcing them.
feature-development
Workflow command scaffold for feature-development in marketing-council-pack.
feature-flags
Design feature flag strategy with lifecycle management. Usage - /mindforge:feature-flags [feature] [--type release|experiment|operational] [--rollout 5%].