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 skills add wei63w/pm-manager --skill pm-testsgit clone --depth 1 https://github.com/wei63w/pm-managerWrote 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/skills/wei63w/pm-manager/pm-tests)<a href="https://agentmods.dev/skills/wei63w/pm-manager/pm-tests"><img src="https://agentmods.dev/badge/skills/wei63w/pm-manager/pm-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.
<a href="https://agentmods.dev/skills/wei63w/pm-manager/pm-tests"><img src="https://agentmods.dev/badge/skills/wei63w/pm-manager/pm-tests.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00027 | $0.00308 |
| Opus 5.5 | $0.00011 | $0.00123 |
| Sonnet 5.5 | $0.00005 | $0.00062 |
| Haiku 4.5 | $0.00003 | $0.00031 |
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 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.
What it actually says
User Input
$ARGUMENTS
Outline
/pm-tests 只管单测缺口。用户以中文交互时用中文回复。未确认不得把测试文件写入业务树。
- Require
.pm/。缺则建议/pm-init。 - 先读
.pm/architecture/map.json与.pm/state/test-gaps.md（若有）。禁止为找测试做无过滤全库递归。 - 运行
pm tests，列出核心源 / 本轮变更缺少的配套测试，以及建议落点。 - 只报告。若用户要求起草，先给出方案，停下等确认后再写测试文件。
- Closing：
_closing.md轻量档。指向test-gaps.md。
Done When
- 缺口已列出（或明确没有）
- 未自动创建业务树测试文件
Shared Workflow
Map-first. Confirm-before-write for test files. Design baseline: docs/prd.md + 宪章。
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 · 35 lines · 27 tokens per session scan A e171f2a765c4
pm-tests is a skill published in the GitHub repository wei63w/pm-manager (87 stars, last pushed 1mo ago), licensed MIT. It adds 27 tokens to every session and 308 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
awesome-test-writing
Designs and writes tests that catch real regressions: unit, integration or E2E placement, fixtures, behavior-first assertions, characterization and property tests. Use when asked to write tests, add coverage or a regression test.
aif-test
Run unit, integration, e2e and UI tests with coverage analysis, build verification, visual regression and QA reports.
aif-web-testing
Test web apps with Playwright, Vitest and k6: E2E, unit, integration, load, security, visual and a11y.
crucible
Write solid unit tests using property-based testing and mutation testing. Use whenever unit tests are being written, fixed, audited, or reviewed in a TypeScript project; whether the user asks directly or test-writing occurs as a step inside another workflow (TDD, feature implementation, bug fixing, code review). Also…
migrate-to-shoehorn
Migrate test files from as type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace as in tests, or needs partial test data.
test-driven-development
Drives development with tests using the red-green-refactor loop. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality. Use when asked to add tests to a function, fix a bug…