pm-tests

A test-gap checker for projects using a `.pm` project-management folder. It identifies core or recently changed source files that do not have matching unit tests, meaning small tests that check individual pieces of code.

In plain words
What is it for?
Use it to list missing unit-test companions, review suggested test locations, and request test drafts after deciding what should be added.
Why use it?
It shows where test coverage may be missing without creating files in the application codebase before you approve that work.

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/wei63w/pm-manager/pm-tests
Clone the repo
git clone --depth 1 https://github.com/wei63w/pm-manager
Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 302 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.00024 $0.00302
Opus 5 $0.00012 $0.00151
Sonnet 5 $0.00005 $0.00060
Haiku 4.5 $0.00002 $0.00030

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

Security

Grade A, and why

pm-tests 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

  • tests — 100% identical, 0 lines differ
adapters/claude-code/commands/pm-tests.md · 34 lines

What it actually says

User Input

$ARGUMENTS

Outline

/pm-tests 只管单测缺口。用户以中文交互时用中文回复。未确认不得把测试文件写入业务树。

  1. Require .pm/。缺则建议 /pm-init
  2. 先读 .pm/architecture/map.json.pm/state/test-gaps.md(若有)。禁止为找测试做无过滤全库递归。
  3. 运行 pm tests,列出核心源 / 本轮变更缺少的配套测试,以及建议落点。
  4. 只报告。若用户要求起草,先给出方案,停下等确认后再写测试文件。
  5. Closing:_closing.md 轻量档。指向 test-gaps.md

Done When

  • 缺口已列出(或明确没有)
  • 未自动创建业务树测试文件

Shared Workflow

Map-first. Confirm-before-write for test files. Design baseline: docs/prd.md + 宪章。

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 · 34 lines · 24 tokens per session scan A 07ee6b768211

Subscribe to this mod's changes

pm-tests is a command published in the GitHub repository wei63w/pm-manager (96 stars, last pushed 3d ago), licensed MIT. It adds 24 tokens to every session and 302 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.