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 skills add Today-Hbw/claude-code-dev-workflow --skill implementgit clone --depth 1 https://github.com/Today-Hbw/claude-code-dev-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/skills/today-hbw/claude-code-dev-workflow/implement)<a href="https://agentmods.dev/skills/today-hbw/claude-code-dev-workflow/implement"><img src="https://agentmods.dev/badge/skills/today-hbw/claude-code-dev-workflow/implement/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/skills/today-hbw/claude-code-dev-workflow/implement"><img src="https://agentmods.dev/badge/skills/today-hbw/claude-code-dev-workflow/implement.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.00017 | $0.00836 |
| Opus 5.5 | $0.00007 | $0.00334 |
| Sonnet 5.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 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.
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.
- 1mo 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 (23 stars, last pushed 2mo ago), licensed MIT. It adds 17 tokens to every session and 836 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-30.
Other skills, from other repositories
tdd
A reference for Test-Driven Development (TDD), a method where you write a failing test, make it pass, and then improve the code. It covers how to write durable tests, where to place them, and which patterns to avoid.
tdd
Guidance for test-driven development (TDD), a method where you write a failing test, make it pass with a small change, and then improve the code. It focuses on tests that check user-visible behavior through public interfaces.
pair-programming
AI-assisted pair programming with multiple modes (driver/navigator/switch), real-time verification, quality monitoring, and comprehensive testing. Supports TDD, debugging, refactoring, and learning sessions. Features automatic role switching, continuous code review, security scanning, and performance optimization with…
hotfix
Fixes an observed defect with reproducible evidence in one call: writes a short trace doc before touching code, implements the fix, and backs it with a regression test written before the fix. Production incidents are the motivating case, not a gate. When blocked, it halts by name and saves the doc for a later call to…
web-dev-standards
Use when designing software architectures ('codebase-design' Deep Modules/Design-It-Twice), writing tests ('test-driven-development' mock boundaries), creating setup scripts ('interactive-wizard'), applying TypeScript, Next.js, Expo, or monorepo standards, or configuring shared-domain Resend email…
lfe-tdd
Red-green-refactor quality pass on code the Builder just wrote. Use in the Builder sub-pipeline after lfe-builder completes implementation.