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 skills/today-hbw/claude-code-dev-workflow/summarynpx skills add Today-Hbw/claude-code-dev-workflow --skill summarygit clone --depth 1 https://github.com/Today-Hbw/claude-code-dev-workflowWhat 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.00034 | $0.00862 |
| Opus 5 | $0.00017 | $0.00431 |
| Sonnet 5 | $0.00007 | $0.00172 |
| Haiku 4.5 | $0.00003 | $0.00086 |
Grade A, and why
summary 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 2d 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
总结 · 输出格式
你的任务
在整个流程完成后，生成 总结.md，记录本次开发的全部交付物和关键信息。
输出格式
参考以下模板生成 总结.md：
# <项目名称>（<负责人>）· 开发总结
> 日期：<日期> ｜ 范围：<本次涉及的任务列表>
## 一、交付文件
### Story A <任务 1 名称>（IDxxxxxxx）
- `<文件路径 1>` — <简要说明>
- `<文件路径 2>` — <简要说明>
- `<文件路径 3>`
- <具体改动点 1>
- <具体改动点 2>
### Story B <任务 2 名称>（IDxxxxxxx）
- `<文件路径 1>` — <简要说明>
- `<文件路径 2>` — <简要说明>
## 二、上线前依赖（业务方/其他人）
1. **<依赖 1>**：<说明>
2. **<依赖 2>**：<说明>
## 三、设计要点
- <关键设计决策 1>
- <关键设计决策 2>
- **视觉规格落地**（涉及 UI 时）：按 PRD 截图/原型落地的位置与文案，逐项对齐记录（列归属/合并、按钮精确文案、所在页签、筛选与字段顺序）；与图不一致或图中未给、由我方拍板的，单独标出并说明理由
## 四、已知待联调
- <需要和其他人联调的事项>
- <需要验证的功能点>
格式要求
- 头部署名：标题中的「负责人」取第 0 步解析出的个人标识（
person） - 交付文件：按任务分组，列出所有修改/新增的文件
- 上线前依赖：需要其他人/业务方配合的事项
- 设计要点：关键技术决策和理由
- 已知待联调：还没验证、需要联调的事项
写入规则
- 文件路径：
<session_dir>/总结.md - 编码：UTF-8
- 如果文件已存在，询问用户是覆盖还是追加
维护工作区 总览.md（可选，需 --overview）
仅当本次运行传入 --overview 才执行；否则跳过。 完整规则（定位、项目分组、写行、新建模板）见 dev-flow 命令的「总览维护」章节。
本步执行其中的收尾触点：生成 总结.md 后，把本次需求从「🔥 在办」移到对应项目的「✅ 已完成」，状态 ✅，产出列填本次会话目录的相对链接，并更新顶部日期。若开始时（第 1 步）因未定位到 Prd/ 工作区而跳过登记，则本步同样跳过。
注意事项
- 交付文件要写完整路径，不要遗漏；涉及 UI 的改动，简要说明要点出落点（进哪列/是否合并、按钮文案、所在页签）
- 上线依赖要写清楚责任方
- 设计要点要简洁，说清楚「为什么这么做」
- 待联调项要具体，便于后续追踪
- 更新每个任务的
计划.md状态为「已完成（详见 ../总结.md）」
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.
- 2d ago First seen · 76 lines · 34 tokens per session scan A e4303a79803d
summary is a skill published in the GitHub repository Today-Hbw/claude-code-dev-workflow (22 stars, last pushed 21d ago), licensed MIT. It adds 34 tokens to every session and 862 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-30.
Other skills, from other repositories
metrics-instrumentation
Specification for instrumenting an opik-backend workflow with operational OpenTelemetry metrics — per-stage throughput/latency/error counters and native histograms, dimensioned per-customer (workspace). Use when a pipeline (scoring, ingestion, experiments, jobs) needs per-stage visibility. Covers metric emission only…
happiness-skill
当用户问「怎么才能更幸福/为什么得到了还不满足/怎么减少焦虑」时调用。 核心理念: 幸福是缺憾感清空的默认状态, 是可训练的技能; 欲望是与自己的契约(得到前不快乐), 同时只留一个重大欲望; 活在当下。 不适用于: 临床抑郁等需要专业治疗的场景(本书方法不能替代医疗)。 Triggers: 幸福/不快乐/欲望/焦虑/知足/活在当下/happiness/desire/anxiety.
short-drama-storyboard
把剧本和视觉事实转成有镜头职责、空间连续性和可冻结起点的 剧集/ /分镜.md。 每镜使用二级标题 ## SHOT-...，同镜下用 ### 冻结关键帧提示词 写起始帧正文。.
seedance-prompt
This skill should be used when the user asks to write, improve, translate, compress, or debug a Seedance 2.0 video prompt; mentions T2V, I2V, V2V, R2V, camera direction, prompt quality, or provides reference assets for a production-ready prompt.
setup-matt-pocock-skills
为本仓库配置工程技能——设置其 issue tracker、分诊标签词汇表和领域文档布局。首次使用其他工程技能前运行一次。.
deep-review
Parallel competency-based code review. Launches independent Agent reviewers per competency (security, performance, architecture, database, concurrency, error-handling, frontend, testing), each with a focused checklist and isolated context. Synthesizes findings into unified report with FIX/DEFER/ACCEPT triage. Use…