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.
git 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/commands/wei63w/pm-manager/check)<a href="https://agentmods.dev/commands/wei63w/pm-manager/check"><img src="https://agentmods.dev/badge/commands/wei63w/pm-manager/check/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/commands/wei63w/pm-manager/check"><img src="https://agentmods.dev/badge/commands/wei63w/pm-manager/check.svg" alt="Reviewed on agentmods" width="80" 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.00031 | $0.00470 |
| Opus 5.5 | $0.00012 | $0.00188 |
| Sonnet 5.5 | $0.00006 | $0.00094 |
| Haiku 4.5 | $0.00003 | $0.00047 |
Grade A, and why
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 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.
This is a copy
100% identical to pm-check — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
User Input
$ARGUMENTS
Accepted: repair | empty (diagnose only).
Outline
/pm-check is the recovery command. Prefer pm check from the project root and explain the table in Chinese.
- If
.pm/is missing: block → 请先/pm-init或pm init。Do not treat as a new empty project silently. - Read
pm checkoutput. Also inspect:project.yaml/prd.status(draft → 提醒 confirm / skip,不自动当基线).pm/state/audit.jsonl是否可逐行 JSON 解析.pm/architecture/map.json是否存在、是否能解析.pm/engineering/reviews.md待处置条数- 核心文档索引是否过期(
pm docs只更新索引)
- If the user said
repair(or agrees after you list issues):- Re-run
pm init --scaffold-only --no-skills-shto fill missing skeleton only (CLI is copy-if-missing). - Never overwrite user-edited or
prd.status=confirmed/charter.status=approvedcontent. - Rebuild map with
pm archif missing or unreadable. - Rebuild dashboard with
pm dashboardif missing. - If
audit.jsonlis corrupt: keep a.bakof the readable prefix if possible; do not silently truncate confirmed reviews/todos.
- Re-run
- Tell the user what was repaired vs what needs a human confirm.
- Closing:
_closing.md轻量档。
Done When
- Missing
.pm/directed to/pm-init - Diagnosis listed in Chinese
- Repair path did not overwrite confirmed baselines
Shared Workflow
Map-first. Redact. No auto-write of app code. 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 · 42 lines · 31 tokens per session scan A 76d622819348
check is a command published in the GitHub repository wei63w/pm-manager (88 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 470 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to pm-check, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
bug
Turn a description of something broken into a GitHub issue of type Bug. Drafts a structured report, previews it, and files it only after you confirm — typed Bug where the repo supports issue types, otherwise labelled bug.
incident-triage
Triage a concrete technical failure (stack trace, failing test, runtime symptom, production alert), classify it and pick a fix size (HOTFIX/SLICE/INVESTIGATION/ESCALATE). Use when there is concrete failure evidence, an active task folder exists, and urgency is real or unclear, or hotfix versus full flow is unclear. Do…
state-reconcile
Detect drift between TASKSTATE.md, task artifacts, and reality (code, tests, diff), then propose the minimum updates. Also has an opt-in read-only memory-lint mode. Use when TASKSTATE.md is stale or inconsistent, plan or slice files disagree, you need a full cross-check before routing or delivery, or you want a…
feedback-to-closure
Turn raw feedback (reports, Sentry, reviews, QA/audit findings) into deduplicated durable tickets and drive each to production-verified closure.
deadcode-plan
Dead-code audit — configured Knip baseline plus ratchet plan, delete nothing until approved.
postmortem-writeup
Write a blameless incident postmortem that finds the systemic cause and produces real preventive actions.