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.
npx agentmods add commands/hatewx/oh-my-ipd/ipd-statusgit clone --depth 1 https://github.com/hatewx/oh-my-ipdWrote 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/hatewx/oh-my-ipd/ipd-status)<a href="https://agentmods.dev/commands/hatewx/oh-my-ipd/ipd-status"><img src="https://agentmods.dev/badge/commands/hatewx/oh-my-ipd/ipd-status.svg" alt="Measured on agentmods" 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 | $0.00036 | $0.00824 |
| Opus 5 | $0.00018 | $0.00412 |
| Sonnet 5 | $0.00007 | $0.00165 |
| Haiku 4.5 | $0.00004 | $0.00082 |
Grade A, and why
ipd-status 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 4d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IPD-OMO 项目状态查询
作为 LPDT，我需要提供项目的完整状态视图。
状态收集流程
步骤 1: 读取项目状态文件
读取 .claude/project-state.md 获取：
- 项目基本信息
- 当前阶段和迭代
- 历史 TR 记录
- 已知的阻塞和风险
步骤 2: 收集各角色状态
根据 detail_level，收集各角色状态：
- summary: 仅显示各角色的任务完成状态
- detailed: 显示详细的任务内容和阻塞原因
步骤 3: 生成状态报告
生成结构化的状态报告。
输出格式
Summary 级别输出
╔════════════════════════════════════════════════════════════╗
║ IPD-OMO 项目状态 ║
╠════════════════════════════════════════════════════════════╣
║ 项目: [name] | 阶段: [phase] | 迭代: [N/M] ║
╠════════════════════════════════════════════════════════════╣
║ 健康度仪表盘 ║
║ 进度: [🟢🟢🟢🟡⚪] 75% ║
║ 质量: [🟢🟢🟢🟢⚪] 90% ║
║ 成本: [🟢🟢🟡⚪⚪] 60% ║
╠════════════════════════════════════════════════════════════╣
║ PDT 团队状态 ║
║ ├─ LPDT: [监控中] ║
║ ├─ PDU: [Charter 已确认] ║
║ ├─ SE: [LLD 已完成] ║
║ ├─ Dev: [实现中] ║
║ ├─ PQA: [等待提交] ║
║ └─ TMM: [等待提交] ║
╠════════════════════════════════════════════════════════════╣
║ 当前阻塞 ║
║ • [如果有]: [阻塞原因] ║
╠════════════════════════════════════════════════════════════╣
║ 下一步行动 ║
║ • [行动建议] ║
╚════════════════════════════════════════════════════════════╝
Detailed 级别输出
在 Summary 基础上增加：
- 详细的 TR 历史
- 各角色的详细任务列表
- Token 消耗明细
- 风险矩阵
- 建议的决策
交互支持
如果用户查询状态时遇到问题，主动提供：
- 状态缺失: 提示使用
ipd-start初始化项目 - 状态过期: 提示状态文件可能需要更新
- 阻塞求助: 根据阻塞类型提供解决方案
执行指令
请按以下步骤执行：
- 读取
.claude/project-state.md - 根据 detail_level 格式化输出
- 分析当前状态并提供下一步建议
- 如果有阻塞，明确标识并建议解决方案
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.
- 4d ago First seen · 86 lines · 36 tokens per session scan A 42a86a1f68a0
ipd-status is a command published in the GitHub repository hatewx/oh-my-ipd (6 stars, last pushed 2mo ago), licensed MIT. It adds 36 tokens to every session and 824 once invoked, about $0.0002 per session on Opus 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
checkpoint
Export, refresh, verify, or import a comprehensive cross-topic Project Knowledge Checkpoint for a repository, with privacy checks.
portfolio
Show a read-only hub-wide portfolio of canonical Ideas and active Projects without duplicating topic-owned records.
cycle-design
Design a cycle — create new cycles with planned stories, detail existing planning cycles, or quick-sketch a roadmap. Detects planning docs in .craft/planning/ and sources the cycle from them when relevant.
status
Show current Craft progress — cycles, stories, backlog in a rich dashboard view.
cycle-start
Activate a cycle and start implementing its stories.
story-implement-auto
Autonomous story implementation — auto-picks stories, chains through cycle, no interactive prompts.