Test Coverage Check

Test Coverage Check is a command for Claude Code from lhfer/claude-howto-zh-cn. It costs 11 tokens per session (71 once invoked), scanned A, original, MIT.

A command for checking automated test coverage and test quality. Test coverage shows which parts or paths of a program are exercised by tests.

In plain words
What is it for?
Use it to view coverage, find uncovered paths, assess test quality, suggest edge cases, and check whether critical code has tests.
Why use it?
It helps reveal untested code, missing boundary cases, weak tests, and important application paths without coverage.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the pr-review plugin — 3 commands, 3 agents shipped together

Good fit Use it to view coverage, find uncovered paths, assess test quality, suggest edge cases, and check whether critical code has tests.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/lhfer/claude-howto-zh-cn/check-tests
About the project

Claude Code 中文全面上手指南 is a Chinese-language learning guide for using Claude Code and combining features such as commands, memory, skills, hooks, MCP, subagents, and plugins. It is aimed at Chinese beginners and provides learning paths, examples, and compatibility guidance, while the catalogue entries package parts of that guidance as agent resources.

lhfer/claude-howto-zh-cn · 2,294 stars · on GitHub

Install

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.

Clone the repo
git clone --depth 1 https://github.com/lhfer/claude-howto-zh-cn

Made for: Claude Code.

Or install pr-review, the plugin that ships this one along with the rest of its 3 commands, 3 agents.

Wrote 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.

agentmods badge for Test Coverage Check

README.md
[![agentmods](https://agentmods.dev/badge/commands/lhfer/claude-howto-zh-cn/check-tests/github.svg)](https://agentmods.dev/commands/lhfer/claude-howto-zh-cn/check-tests)
Your own site
<a href="https://agentmods.dev/commands/lhfer/claude-howto-zh-cn/check-tests"><img src="https://agentmods.dev/badge/commands/lhfer/claude-howto-zh-cn/check-tests/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.

agentmods 80×15 button for Test Coverage Check

Your own site · 80×15
<a href="https://agentmods.dev/commands/lhfer/claude-howto-zh-cn/check-tests"><img src="https://agentmods.dev/badge/commands/lhfer/claude-howto-zh-cn/check-tests.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 71 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00011 $0.00071
Opus 5 $0.00005 $0.00036
Sonnet 5 $0.00002 $0.00014
Haiku 4.5 $0.00001 $0.00007

Measured 13d ago against content hash 0f227b0b44fe, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

Test Coverage Check 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 13d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

07-plugins/pr-review/commands/check-tests.md · 13 lines

What it actually says

Test Coverage Check / 测试覆盖检查

  1. 查看覆盖率
  2. 找出未覆盖路径
  3. 判断测试质量
  4. 补边界情况建议
  5. 检查关键路径是否有测试
Changes

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.

  1. 13d ago First seen · 13 lines · 11 tokens per session scan A 0f227b0b44fe

Subscribe to this mod's changes

Test Coverage Check is a command published in the GitHub repository lhfer/claude-howto-zh-cn (2,294 stars, last pushed 1mo ago), licensed MIT. It adds 11 tokens to every session and 71 once invoked, about $0.0001 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.