all

A full technical governance scan for a project, covering its architecture and enabled engineering modules. It records findings, tasks, evidence, and a browser-based dashboard.

In plain words
What is it for?
Use it to inspect architecture, engineering practices, environment, APIs, tests, releases, databases, operations, and costs, then combine the results into tracked findings and tasks.
Why use it?
It gathers technical debt and project risks in one review, while preventing an unconfirmed project plan from being treated as a standard for judging the code.

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/all
Clone the repo
git clone --depth 1 https://github.com/wei63w/pm-manager
Per session 34 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 922 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod 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.00034 $0.00922
Opus 5 $0.00017 $0.00461
Sonnet 5 $0.00007 $0.00184
Haiku 4.5 $0.00003 $0.00092

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

Security

Grade A, and why

all 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

This is a copy

100% identical to pm-all — 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.

skills/pm-manager/templates/commands/all.md · 53 lines

How it starts

The opening of the file, as written. The whole thing — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.

User Input

$ARGUMENTS

Flags: --compare-baseline | --skip-charter-gate (default technical mode) | --modules=... | --path=... | --verbose.

Outline

Default mode is a technical debt scan. Do not block on prd.status=draft. Unconfirmed PRD/charter must not be used to judge “是否合理”.

  1. Gate: .pm initialized? else block → recommend /pm-init.
  2. Modes:
    • Technical (default): scan architecture + enabled modules. --skip-charter-gate is an alias of this default.
    • Baseline compare (--compare-baseline): only if prd.status=confirmed or charter.status=approved. If still draft, wait and offer confirm / revise / skip / 继续技术扫描.
  3. Run module scans (arch, engineering, env, api, test, release, db, ops, cost) then bugs if log sources/--path/paste exist; else skip bugs with recommendation.
    • Architecture step must produce diagrams and .pm/architecture/map.json: run pm arch / /pm-arch.
    • Module deep-scan internals live in templates/commands/discover.md — do not tell the user to run /pm-discover.
  4. Merge findings/todos; write evidence/scans/pm-all-*.json. 4b. Qualified reviews: every finding written to .pm/engineering/reviews.md MUST include reasoning + cited snippet. Unqualified rows MUST NOT enter rules.md. If there is no local diff, say there is nothing to review. Load enabled rules from .pm/engineering/rules.md. Only disposition=confirmed may become rules. P0/blocking MUST interrupt; P1/P2 stay in the report. Prefer /pm-review for a dedicated review pass. Full checkup is /pm-checkup only — do not run it here by default.
  5. Rebuild the dashboard (required):
    • Prefer running: pm dashboard (from project root)
    • Output: .pm/dashboard/index.htmloverview.mdfindings.mdtodos.mdstats.json
  6. Chat summary (中文): all blocking+high todos (no 3-item cap) unless --verbose.
  7. Closing: _closing.md 完整档;只列已生成文件。
  8. Finish with /pm-status style Chinese health line.

Read the full file on GitHub · 53 lines

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 · 53 lines · 34 tokens per session scan A 31ad0904f19f

Subscribe to this mod's changes

all is a command published in the GitHub repository wei63w/pm-manager (96 stars, last pushed 2d ago), licensed MIT. It adds 34 tokens to every session and 922 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to pm-all, differing in 0 lines, and is treated as a copy.