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/implementnpx skills add Today-Hbw/claude-code-dev-workflow --skill implementgit 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.00017 | $0.00836 |
| Opus 5 | $0.00009 | $0.00418 |
| Sonnet 5 | $0.00003 | $0.00167 |
| Haiku 4.5 | $0.00002 | $0.00084 |
Grade A, and why
implement 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
编码实现 · 方法论
你的任务
按照需求理解和对齐结论实施编码。核心思路：垂直切片——每个切片走通全链路，而非按层水平推进。
核心方法：垂直切片（Tracer Bullet）
将任务拆分为垂直切片：
❌ 水平切片（错误方式）：
先做数据层：表 A、表 B、表 C
再做接口层：API 1、API 2、API 3
最后做展示层：页面 X、页面 Y、页面 Z
✅ 垂直切片（正确方式）：
切片 1：表 A → API 1 → 页面 X（走通一条完整路径）
切片 2：表 B → API 2 → 页面 Y（又一条完整路径）
切片 3：表 C → API 3 → 页面 Z（最后一条路径）
每个切片完成后可以独立演示或验证，不依赖其他切片。
编码循环：RED → GREEN → REFACTOR
有测试框架的项目，每个切片内跑 TDD 循环：
RED → 写一个描述行为的测试，运行，确认失败
GREEN → 写最小实现让测试通过，不多写
REFACTOR → 测试通过后重构，消除重复，保持测试绿色
规则：
- 一次只处理一个切片
- 一个切片内，一次只写一个测试
- 只写让当前测试通过的最小代码
- 不要预测后续切片需要什么
- RED 状态下绝不重构——先 GREEN，再重构
测试运行节奏
- 每次提交前：跑类型检查（
npm run typecheck或等效命令） - 每个切片完成后：跑该切片相关的测试文件
- 所有切片完成后：跑完整测试套件
- 如果发现测试失败：立即修复，不要积累
执行流程
- 回顾对话上下文中的任务列表和验收标准（来自第 1 步读 PRD + 第 2 步提问对齐的结论）
- 拆分为垂直切片：每个切片走通一条完整的 数据→接口→展示→测试 路径
- 按依赖顺序执行切片（无依赖的切片先做）
- 每个切片内：
- 写测试（RED）
- 写实现（GREEN）
- 重构（REFACTOR）
- 跑测试确认绿色
- 所有切片完成后：跑完整测试套件
- 用 TodoWrite 更新进度
无测试框架的项目
如果项目没有测试框架，跳过 TDD 循环，但仍然保持垂直切片思路：
- 每个切片完成后手动验证核心路径
- 用日志/打印确认数据流转正确
- 切片粒度可以稍大（以可手动验证为单位）
注意事项
- 遵循项目现有的代码风格和规范（对齐周边代码的命名、缩进、惯用法）
- 不要在一次编码中做所有事，按切片逐步推进
- 每完成一个切片，用 TodoWrite 更新进度
- 完成后进入步骤 4（Code Review）
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 · 83 lines · 17 tokens per session scan A 20d2c22f53cd
implement is a skill published in the GitHub repository Today-Hbw/claude-code-dev-workflow (22 stars, last pushed 21d ago), licensed MIT. It adds 17 tokens to every session and 836 once invoked, about $0.0001 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…