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/sdsrss/gsd-liteWrote 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/sdsrss/gsd-lite/prd)<a href="https://agentmods.dev/commands/sdsrss/gsd-lite/prd"><img src="https://agentmods.dev/badge/commands/sdsrss/gsd-lite/prd/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/sdsrss/gsd-lite/prd"><img src="https://agentmods.dev/badge/commands/sdsrss/gsd-lite/prd.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.00025 | $0.00857 |
| Opus 5.5 | $0.00010 | $0.00343 |
| Sonnet 5.5 | $0.00005 | $0.00171 |
| Haiku 4.5 | $0.00003 | $0.00086 |
Grade A, and why
prd 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 5d 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.
What it actually says
STEP 0 — 已有项目检测
调用 health 工具(MCP tool 名称: health)。如果返回 state_exists=true 且项目未完成/未失败:
- 告知用户: "检测到进行中的 GSD 项目。"
- 显示当前项目状态 (项目名、当前阶段、workflow_mode)
- 提供选项:
- (a) 恢复现有项目 → 转到
/gsd:resume - (b) 覆盖并重新开始 → 继续 STEP 1(现有 state.json 将被覆盖:后续
state-init必须带force: true,否则会返回STATE_EXISTS且什么也不做) - (c) 取消
- (a) 恢复现有项目 → 转到
- 等待用户选择后再继续
如果无 state 或项目已完成/已失败 → 直接进入 STEP 1。
STEP 1: 解析输入
判断 $ARGUMENTS 的类型:
如果是文件路径 (包含 / 或 . 且文件存在):
- 使用 Read 工具读取文件内容
- 如果文件不存在:
- 告知用户文件不存在
- 提示常见原因: 路径拼写错误、当前工作目录不正确
- 建议: "请确认文件路径,或使用绝对路径重试。需要我帮你查找文件吗?"
- 停止
如果是文本描述:
- 直接作为需求描述使用
STEP 2: 分析代码库
- 使用 Glob/Grep/Read 分析代码库中与需求相关的部分
- 识别: 已有代码结构、技术栈、现有约定
- 目的: 让后续计划能与现有代码库无缝衔接
STEP 3: 提取关键需求点
- 从输入内容中提取所有关键需求点
- 整理为结构化列表
- 向用户确认理解是否正确:
- "以下是我从需求中提取的关键点,请确认:"
- 逐条列出,标注优先级
STEP 4: 提出补充问题
- 基于需求分析,识别模糊点和缺失信息
- 提出补充问题,每个问题提供选项:
- 标识推荐选项
- 允许用户自定义回答
- 使用提问技巧 (如可用): 调用
health工具取docs.references, Read<docs.references>/questioning.md - 用户回答后,可适当追问直到需求清晰
调用 health 工具取 docs.workflows,Read <docs.workflows>/execution-flow.md,严格按照其中 STEP 5-12 执行。
<orchestrator_rules>
编排器纪律
- 只有编排器写 state.json,子代理不直接写
- 所有摘要/提示在展示时从 canonical fields 推导,不持久化 derived fields
- 子代理返回结构化 JSON,不解析自然语言
- 上下文 < 35% → 保存状态 + workflow_mode = awaiting_clear + 停止执行 </orchestrator_rules>
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.
- 5d ago Changed · -55 tokens per session c07dc7b21526
- 1mo ago Changed bd3c5935965f
- 1mo ago Changed 52b760d142a8
- 1mo ago First seen · 84 lines · 80 tokens per session scan A 7fb73eb657cd
prd is a command published in the GitHub repository sdsrss/gsd-lite (4 stars, last pushed 2d ago), licensed MIT. It adds 25 tokens to every session and 857 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-31.
Other commands, from other repositories
check-approvals
Check pending approvals and send reminders where overdue. "who still owes an approval".
save
Save current work state for next session. Creates/updates .planning/ files (CHECKPOINT.md, STATE.md, settings.json) so Heimdall resumes with full context. NOT a rewind — saves forward progress. Run before closing a session or at any milestone.
status
Show current Heimdall state — project phase, active agents, quality gates, conflicts.
finish-tasks
Finalize a work item after all tasks are done — cleanup (currently closing the ticket) and mark the work complete.
create-ticket
Create a work-item ticket (GitHub issue / Jira) from an existing requirements.md, then promote its draft spec folder to docs/specs/ /.
finalize
Finalize the month and package approved content for delivery. "close out the month".