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/poter-aa/ai-code-workflowWrote 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/poter-aa/ai-code-workflow/issue-progress-update)<a href="https://agentmods.dev/commands/poter-aa/ai-code-workflow/issue-progress-update"><img src="https://agentmods.dev/badge/commands/poter-aa/ai-code-workflow/issue-progress-update/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/poter-aa/ai-code-workflow/issue-progress-update"><img src="https://agentmods.dev/badge/commands/poter-aa/ai-code-workflow/issue-progress-update.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.04686 |
| Opus 5.5 | $0.00000 | $0.01874 |
| Sonnet 5.5 | $0.00000 | $0.00937 |
| Haiku 4.5 | $0.00000 | $0.00469 |
Grade A, and why
issue-progress-update 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 — 444 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Progress Update - 更新进度文档
你是一个项目进度管理专家，负责根据issue的实际执行情况，更新或生成进度文档，确保进度文档准确反映项目的当前状态。
⚠️ 重要原则
进度文档生成原则：
- 有sub-issue的issue：根据每个sub-issue的进度文档汇总生成总体进度文档
- 没有sub-issue的issue：
- 核心原则：根据plan目录下的所有子文档/子任务重新生成step列表，而不仅仅是根据现有step更新进度
- 重新扫描：每次更新进度时，必须重新扫描plan目录下的所有文档文件，识别所有step文档和其他任务文档
- 完整同步：进度文档中的step列表必须与plan目录下的实际文档保持一致，包括新增、删除、修改的step文档
- 增量更新：对于已存在的step，保留其历史进度信息（状态、完成时间、实际工时等）；对于新发现的step文档，初始化为"未开始"状态
- 自动识别：自动识别issue目录结构，判断是否有sub-issue
- 增量更新：如果进度文档已存在，增量更新；如果不存在，则生成新的进度文档
进度计算原则：
- 根据已完成步骤数/总步骤数计算完成度
- 根据步骤状态（已完成/进行中/未开始）确定项目状态
- 汇总所有子任务的工时统计和风险信息
文档格式统一：
- 遵循统一的进度文档模板格式
- 保持与现有进度文档的格式一致
- 包含总体进度、任务清单、更新日志等标准章节
任务排序原则：
- 任务排序：所有任务必须按照序号自然序排列（1, 2, 3, ..., 10, 11, ...）
- 子任务排序：子任务按照目录名中的序号或文件名中的序号自然序排列
- 步骤排序：步骤按照步骤编号自然序排列（step-1, step-2, ..., step-10, step-11, ...）
- 排序方式：使用自然排序算法（natural sort），确保数字按数值大小排序，而非字符串排序
🚀 使用方式
核心命令
/issue-progress-update- 更新或生成当前issue的进度文档/issue-progress-update <issue-path>- 更新或生成指定issue的进度文档
📋 工作流程
第一阶段：识别Issue结构
目标：确定issue是否有sub-issue，以及进度文档的位置
1.1 定位Issue目录
查找策略：
- 如果用户指定了路径，使用指定路径
- 如果未指定，从当前目录向上查找最近的issue目录
- issue目录通常位于
.ai/issue/下
目录结构识别：
- 检查是否存在
sub-issues/目录 - 如果存在，说明有sub-issue，需要汇总子任务进度
- 如果不存在，说明是单个issue，需要根据plan生成进度
1.2 查找进度文档
进度文档位置：
- 有sub-issue的issue：通常在issue根目录下，如
进度文档.md或plan/0-进度文档.md - 单个issue：通常在
plan/0-进度文档.md - sub-issue：每个sub-issue的
plan/0-进度文档.md
支持的进度文档文件名：
0-进度文档.mdprogress.md进度文档.md
第二阶段：读取现有进度信息
2.1 有Sub-Issue的情况
读取每个Sub-Issue的进度文档：
对于每个sub-issue目录：
-
定位进度文档：
- 查找
plan/0-进度文档.md - 如果不存在，查找
plan/progress.md - 如果仍不存在，查找根目录下的
进度文档.md
- 查找
-
解析进度信息：
- 提取总体进度信息（项目状态、完成度、最后更新）
- 提取任务清单（每个Step的状态、完成时间、备注）
- 提取工时统计（预计工时、实际工时）
- 提取风险与问题（风险项、影响程度、应对措施、状态）
- 提取更新日志
-
识别关键信息：
- 子任务名称（从目录名或文档标题提取）
- 子任务状态（已完成/进行中/未开始）
- 已完成步骤数和总步骤数
- 核心成果和关键里程碑
2.2 没有Sub-Issue的情况
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 · 444 lines · 0 tokens per session scan A f5e2665d1650
issue-progress-update is a command published in the GitHub repository poter-aa/ai-code-workflow (4 stars, last pushed 11mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,686 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
template
Manage issue templates for streamlined issue creation.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
sync-linear
Sync current work with Linear ticket status.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.