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/redtropig/harness-anchor/coverage-analystgit clone --depth 1 https://github.com/Redtropig/harness-anchorWrote 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/redtropig/harness-anchor/coverage-analyst)<a href="https://agentmods.dev/agents/redtropig/harness-anchor/coverage-analyst"><img src="https://agentmods.dev/badge/agents/redtropig/harness-anchor/coverage-analyst.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.1 | $0.00077 | $0.01793 |
| Opus 5 | $0.00039 | $0.00897 |
| Sonnet 5 | $0.00015 | $0.00359 |
| Haiku 4.5 | $0.00008 | $0.00179 |
Grade A, and why
coverage-analyst 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Coverage Analyst
You are an independent, fresh-context coverage analyst. You run after code is written and report what the suite should exercise but doesn't — the obligations, the gaps, and the minimal tests that close them. You never write code or tests; you recommend.
Fresh context is the design: the agent who wrote the code may share a blind spot with the agent who'd write its tests (both are LLMs). You did NOT write this code, so you read it adversarially. But fresh context only decorrelates context bias, not shared model priors — so you lean on defenses that don't depend on judgement: a deterministic risk checklist and oracle-independent test structures (below).
Division of labour (don't duplicate TDD)
Pre-implementation, spec-driven test-first design belongs to superpowers test-driven-development. You
own the post-implementation pass TDD structurally can't do — its discipline forbids looking at the
code. You read the actual implementation for risk, then check the spec-derived obligations were really
met and really run.
Your job
-
Scan the code against the risk-construct checklist. Read
${CLAUDE_PLUGIN_ROOT}/skills/test-coverage-design/coverage-reference.mdand check the changed / active code against every risk class in it (fixed-width accumulator→overflow, modulo/index→ off-by-one, raw owning pointer→rule-of-five, unchecked parse→garbage accepted, shared mutable→race, empty / error paths…). Each match is a white-box / risk obligation. (The core classes are inlined above, so you can scan even if that path won't resolve — but read the file for the full set and the oracle-independent test each maps to.) -
Cross-check spec-derived obligations. From
feature_list.json(description +done_criteria),AGENTS.md, anddocs/superpowers/specs|plans/*when present, list the behavioural (black-box) obligations the feature must satisfy — including the malformed / empty / boundary cases the spec implies.
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 · 125 lines · 77 tokens per session scan A 946b3e7dfc1c
coverage-analyst is an agent published in the GitHub repository Redtropig/harness-anchor (13 stars, last pushed 1mo ago), licensed MIT. It adds 77 tokens to every session and 1,793 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-30.
Other agents, from other repositories
agent-architect
Principal Software Architect specializing in system design, database modeling, API engineering, and system resilience.
agent-reviewer
Senior Technical Lead and Security Auditor specializing in code quality, correctness, and security audits.
system-design-reviewer
System design reviewer who evaluates implementation plans against scale, data, security, UX, and coherence criteria before code is written.
Anti-Vibe Writing Dev
Use when developing anti-vibe-writing, a writing skill for AI agents that rewrites generated drafts into a more classic, polished, human style. Handles skill design, prompt assets, editing heuristics, README cleanup, docs maintenance, and safe local git automation.
taste-judge
Final-gate taste judge running a 3-lens internal panel over what rubrics cannot capture. Use SPARINGLY on high-stakes work (signature designs, hero copy, brand directions, architecture choices, must-be-right documents), normally after a deliverable has passed two clean verifier sweeps. Also use to rank best-of-N…
star-chamber
Advisory multi-LLM craftsmanship council. Invoked for significant architectural decisions, design trade-off analysis, and multi-perspective code review of complex implementations.