test-coverage

A test-coverage tool measures which parts of the code tests exercise and creates tests for uncovered code paths.

In plain words
What is it for?
Use it to find weakly tested files and add unit, API integration, and end-to-end tests for normal cases, errors, and edge cases such as empty or missing values.
Why use it?
It shows where tests are missing and helps raise overall coverage to the stated 80% target.

Command

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.

agentmods
npx agentmods add commands/luohaothu/everything-codex/test-coverage
Clone the repo
git clone --depth 1 https://github.com/Luohaothu/everything-codex
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 196 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.00196
Opus 5 $0.00000 $0.00098
Sonnet 5 $0.00000 $0.00039
Haiku 4.5 $0.00000 $0.00020

Measured 2d ago against content hash 559b838dacb4, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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.

docs/zh-CN/commands/test-coverage.md · 29 lines

What it actually says

测试覆盖率

分析测试覆盖率并生成缺失的测试:

  1. 运行带有覆盖率的测试:npm test --coverage 或 pnpm test --coverage

  2. 分析覆盖率报告 (coverage/coverage-summary.json)

  3. 识别覆盖率低于 80% 阈值的文件

  4. 对于每个覆盖率不足的文件:

    • 分析未测试的代码路径
    • 为函数生成单元测试
    • 为 API 生成集成测试
    • 为关键流程生成端到端测试
  5. 验证新测试通过

  6. 显示覆盖率指标的前后对比

  7. 确保项目整体覆盖率超过 80%

重点关注:

  • 正常路径场景
  • 错误处理
  • 边界情况(null、undefined、空值)
  • 边界条件
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. 2d ago First seen · 29 lines · 0 tokens per session scan A 559b838dacb4

Subscribe to this mod's changes

test-coverage is a command published in the GitHub repository Luohaothu/everything-codex (24 stars, last pushed 21d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 196 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.