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/pm-init)<a href="https://agentmods.dev/commands/wei63w/pm-manager/pm-init"><img src="https://agentmods.dev/badge/commands/wei63w/pm-manager/pm-init/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/pm-init"><img src="https://agentmods.dev/badge/commands/wei63w/pm-manager/pm-init.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.00035 | $0.02379 |
| Opus 5.5 | $0.00014 | $0.00952 |
| Sonnet 5.5 | $0.00007 | $0.00476 |
| Haiku 4.5 | $0.00003 | $0.00238 |
Grade A, and why
pm-init 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- init — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
Accepted extra words: confirm | approve | revise: <notes> | skip | a one-line project intent.
Outline
You are running /pm-init for the current workspace project root.
User-facing replies must be Chinese when the user writes Chinese. Command names stay /pm-*.
1. Scaffold
Preferred: pm init <root> (creates .pm/, git exclude, adapters). CLI no longer runs skills.sh unless --skills-sh.
Fallbacks: npx @wei63w/pm-manager init, scripts/powershell/create-pm-scaffold.ps1, python scripts/python/create_pm_scaffold.py, or copy templates/pm/ by hand.
Do not overwrite user-edited files under .pm/. Never overwrite prd.status=confirmed or charter.status=approved.
2. Lifecycle and type
new: empty or scaffold-only (README /.gitonly, no business source).existing: build files,src/app/lib, or app config present.
If project.type is unknown / empty, infer from manifests (package.json with vue/nuxt deps → vue, other package.json → node, pyproject.toml → python, go.mod → go, pom.xml / build.gradle → java, Cargo.toml → rust). Do not invent a stack. Write project.lifecycle and project.type on .pm/config/project.yaml. If type is vue and fields still match scaffold defaults, apply Vue frontend seeds (modules.database/operations/cost: false, Vite/Vue runtime on stack, extra scan excludes).
3. Detect Spec Kit (required)
Treat the repo as using Spec Kit only if either exists:
.specify/memory/constitution.md- at least one
.mdunder.specify/specs/
An empty .specify/ directory does not count.
Write speckit.present / constitution / specs on project.yaml.
4. Branch
A. Spec Kit is present
- Map constitution →
.pm/charter/charter.md+ DoD hints. - Map
.specify/specs/**/*.md→.pm/charter/requirements.md(REQ-xxx). - Write
.pm/charter/sources.md. Setcharter.status=draft,source=discovered,prd.source=speckit,prd.status=draft. - Do not invent a competing PRD that disagrees with Spec Kit.
- Stop and ask the user to confirm / revise / skip (Chinese prompt).
- Do not run a module deep-scan yet.
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 · 169 lines · 35 tokens per session scan A 9c411c6cdbc6
pm-init is a command published in the GitHub repository wei63w/pm-manager (88 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 2,379 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 commands, from other repositories
prd
Prepare work for agents: turn a request into an execution-ready issue with requirements, plan, and readiness gate.
board
Inspect, audit, configure, or reconcile a GitHub or Jira project board.
loop
Execute one authorized dispatch:claude prepared issue through executing-plans.
roadmap
Product planning chain: document the ICP, rank the backlog by revenue, and schedule dated milestones.
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.
feature
Turn a rough requirement into one execution-ready feature issue with a plan and readiness verdict.