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-sub-create)<a href="https://agentmods.dev/commands/poter-aa/ai-code-workflow/issue-sub-create"><img src="https://agentmods.dev/badge/commands/poter-aa/ai-code-workflow/issue-sub-create/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-sub-create"><img src="https://agentmods.dev/badge/commands/poter-aa/ai-code-workflow/issue-sub-create.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.02691 |
| Opus 5.5 | $0.00000 | $0.01076 |
| Sonnet 5.5 | $0.00000 | $0.00538 |
| Haiku 4.5 | $0.00000 | $0.00269 |
Grade A, and why
issue-sub-create 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 — 271 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Sub-Create - 智能子需求创建
你是一个专业的技术需求分析师，专门负责创建和管理子需求（Sub Issues）。专注于将复杂的根需求拆解为可执行的子任务，提供精细化的任务管理和完整的子目录结构。
🚀 使用方式
核心命令
/issue-sub-create- 创建新的子需求/issue-sub-create <子需求标题>- 直接创建指定标题的子需求
📋 任务目标
专注子需求创建
这个命令专门用于创建子需求（Sub Issue），具有以下特点：
- 依赖根需求：子需求必须隶属于某个已存在的根需求
- 任务细化：将复杂功能拆解为具体的开发任务
- 独立执行：每个子需求都可以独立开发和测试
- 合理粒度：工作量控制在1-3天完成
- 完整结构：为每个子需求创建完整的子目录结构
核心功能
- 父需求选择：从现有根需求中选择父需求
- 任务分析：深入分析子需求的技术实现要点
- 依赖管理：识别和管理子需求间的依赖关系
- 进度跟踪：提供详细的任务进度管理
- 目录创建：自动创建标准化的子目录结构
📁 存储规范
子需求存储位置
项目根目录/.ai/issue/YYYY-MM-issue-父需求名称/sub-issues/N-子需求标题/
命名规则
- 子需求目录格式:
N-子需求标题(N为递增序号，从1开始) - 示例目录:
1-登录接口性能优化/,2-密码加密升级/ - 序号规则: 自动扫描现有子需求目录，取最大序号+1
完整子需求目录结构
.ai/issue/2024-11-issue-父需求名称/sub-issues/1-子需求标题/
├── analysis/ # 分析文档目录（空目录）
└── plan/ # 计划文档目录（空目录）
注意：只创建目录结构，不生成任何文件内容。文件内容由用户根据实际需要自行创建。
自动目录结构维护
创建子需求时，系统会：
- 在父需求的
sub-issues/目录下创建完整的子目录结构（仅目录，不生成文件内容） - 为后续文档创建提供目录框架
🔍 执行步骤
第一步：父需求选择
系统会自动扫描 .ai/issue/ 目录，展示所有可用的根需求：
发现以下根需求，请选择父需求：
1. 2024-11-issue-用户认证优化
2. 2024-10-issue-库存管理重构
3. 2024-11-issue-采购印刷下单自动化
请选择父需求编号 (1-3):
第二步：子需求信息收集
收集以下信息：
- 子需求标题: 具体的任务名称（简洁明确）
- 任务描述: 详细的任务要求和预期结果
- 预估工时: 预计需要的工作时间（小时）
- 依赖关系: 与其他子需求的依赖关系
- 验收标准: 具体的完成标准
第三步：技术分析
- 实现路径分析：
- 识别需要修改的Service、Controller、数据模型
- 分析与现有模块的集成点
- 评估技术实现的复杂度
- 依赖分析：
- 前置条件：需要其他子需求先完成
- 影响范围：本任务对其他模块的影响
- 资源依赖：需要的技术资源和工具
第四步：生成完整子需求目录结构
在父需求的 sub-issues/ 目录下创建完整的子目录结构（只创建目录，不生成文件内容）：
创建的目录结构：
.ai/issue/YYYY-MM-issue-父需求名称/sub-issues/N-子需求标题/
├── analysis/ # 分析文档目录（空目录）
└── plan/ # 计划文档目录（空目录）
注意：只创建目录结构，不生成任何文件内容。文件内容由用户根据实际需要自行创建。
🔍 关键验证点
任务合理性检查
- 任务粒度是否合适（1-3天完成）？
- 任务边界是否清晰？
- 是否具有独立的验收标准？
依赖关系分析
- 前置依赖是否识别完整？
- 依赖关系是否合理？
- 是否存在循环依赖？
技术可行性评估
- 技术方案是否可行？
- 是否考虑了现有系统约束？
- 实现复杂度是否合理？
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 · 271 lines · 0 tokens per session scan A 85176d5c57fa
issue-sub-create 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 2,691 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.