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/derricktang/pm-workflow-pluginWrote 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/derricktang/pm-workflow-plugin/projectstatus)<a href="https://agentmods.dev/commands/derricktang/pm-workflow-plugin/projectstatus"><img src="https://agentmods.dev/badge/commands/derricktang/pm-workflow-plugin/projectstatus/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/derricktang/pm-workflow-plugin/projectstatus"><img src="https://agentmods.dev/badge/commands/derricktang/pm-workflow-plugin/projectstatus.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.00000 | $0.01202 |
| Opus 5.5 | $0.00000 | $0.00481 |
| Sonnet 5.5 | $0.00000 | $0.00240 |
| Haiku 4.5 | $0.00000 | $0.00120 |
Grade A, and why
projectStatus 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.
How it starts
The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
项目状态简报
你是 AI 产品工作流编排器。用户执行此命令,要求你汇报当前工作流的进展状态。
执行步骤
第一步:读取所有相关文件
使用 Read 工具依次读取以下文件(存在才读取):
process_record/state.md— 工作流状态(必读,从中获取「当前阶段产物」表里各阶段的实际文件路径)- 阶段1成果文件 — 路径从 state.md「当前阶段产物」表中读取(存在则读取前30行了解概况)
- 阶段2成果文件 — 同上
- 阶段3成果文件 — 同上(若存在)
process_record/reviews/stage1_review.md— 阶段1审核(存在则读取审核结论)process_record/reviews/stage2_review.md— 阶段2审核(存在则读取最新审核结论)process_record/reviews/stage3_review.md— 阶段3审核(存在则读取审核结论)process_record/reviews/stage4_review.md— 阶段4审核(存在则读取审核结论)
第二步:展示状态简报
按以下格式向用户汇报:
════════════════════════════════════════════
📊 项目状态简报
════════════════════════════════════════════
需求:[需求摘要]
当前状态:[进行中 / 等待指令 / 已完成]
── 各阶段进度 ──────────────────────────────
阶段1 需求分析:[✅ 已通过 / 🟡 等待产品总监审核 / ⏳ 进行中 / 🔄 整改中 / ⬜ 未开始]
└ 成果文件:[从 state.md 读取,如 outputs/需求分析_报价工具_latest.md] [存在/不存在]
阶段2 功能规划:[✅ 已通过 / 🟡 等待产品总监审核 / ⏳ 进行中 / 🔄 整改中 / ⬜ 未开始]
└ 成果文件:[从 state.md 读取,如 outputs/功能规划_报价工具_latest.md] [存在/不存在]
阶段3 产品定义:[✅ 已通过 / 🟡 等待产品总监审核 / ⏳ 进行中 / 🔄 整改中 / ⬜ 未开始]
└ 成果文件:[从 state.md 读取,如 outputs/产品定义_报价工具_latest.md] [存在/不存在]
阶段4 交付文档:[✅ 已通过 / 🟡 等待产品总监审核 / ⏳ 进行中 / 🔄 整改中 / ⬜ 未开始]
└ 人类可读版:outputs/prd_[产品名]_latest.html [存在/不存在]
└ AI结构化版:outputs/spec_[产品名]_latest.md [存在/不存在]
└ 子产物进度:[仅阶段 4 进行中 / 整改中时显示,从 state.md「阶段4 子产物明细」表读取并**汇总成一行**展示。表 schema 真源:`.claude/commands/newRequirement.md`「阶段4 子产物明细」段(SSOT 双锚 #7,任何 schema 改动须同步本命令展示模板)。例:
"Step 1✅ Step 1.X✅ Step 1.5✅ Step 2✅ Step 2.5✅ Step 3 ⏳ 3/5 模块 / Step 4-7 待启动"
Step 1.X 中段审核整改时显示如 "Step 1.X 🔄 整改中 (2/3)"
**不**逐条展开 12 个子产物,避免报告冗长]
── 当前阶段状态 ──────────────────────────────
[当前所在阶段及具体状态说明,例如:
"阶段2已通过终审,等待 /nextStage 指令继续执行阶段3"
"阶段3进行中,PM已提交成果,等待主管审核"
"阶段3进行中,主管审核不通过,PM正在整改(第N次)"
]
── 待确认问题 ──────────────────────────────
[从 state.md「非阻塞性问题清单」(仅含 ⏳ 待确认开放项)读取条目,简要列出(编号+问题描述);无则写"暂无待确认问题"。已决策条目已移入 `process_record/decisions_ledger.md`,不在本节展示]
── 恢复工作指引 ──────────────────────────────
[根据当前状态给出明确指引,例如:
"输入 /nextStage 可继续执行阶段3"
"回复本次问题后,我将继续当前阶段的执行"
"输入 /nextStage 可重新启动当前阶段"
]
════════════════════════════════════════════
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 · 82 lines · 0 tokens per session scan A d132c2980076
projectStatus is a command published in the GitHub repository derricktang/pm-workflow-plugin (2 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,202 tokens. 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-31.
Other commands, from other repositories
incident-action
Add or resolve action items on an incident. Provided by the Incident Review methodology.
migrate-tasks
Classify existing decompose tasks against a new seed version. Outputs task-migration-plan.yaml with categories (unchanged/modified/deprecated/added). Provided by the Living Spec methodology.
shapeup
A command-based workflow for Shape Up, a product-development method that uses fixed investment limits and work cycles. It manages idea pitches, decisions about which work to build, and progress charts.
pm
Generate a stakeholder-facing PRD from interview results. USE WHEN non-engineering stakeholders need a Product Requirements Document. Optional — most workflows go interview → seed directly.
iteration-drive
Drive the active iteration to completion — Phase 2 Autonomous Execute, Phase 3 iteration-close, Phase 4 Create PR, Phase 5 PR merge-ready loop (prefer babysit/-babysit; optional greploop when repo has it; else CI fallback) until mergeable, then Phase 6 post-merge close once the PR is verified merged. Not Done until…
statuswt
You are checking the status of all active worktree task files in the project.