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 yinqd3/workbuddy-skills --skill subagent-driven-developmentgit clone --depth 1 https://github.com/yinqd3/workbuddy-skillsWrote 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/yinqd3/workbuddy-skills/subagent-driven-development)<a href="https://agentmods.dev/skills/yinqd3/workbuddy-skills/subagent-driven-development"><img src="https://agentmods.dev/badge/skills/yinqd3/workbuddy-skills/subagent-driven-development.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.1 | $0.00059 | $0.00885 |
| Opus 5 | $0.00030 | $0.00443 |
| Sonnet 5 | $0.00012 | $0.00177 |
| Haiku 4.5 | $0.00006 | $0.00089 |
Grade A, and why
subagent-driven-development 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 7d 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
子代理驱动开发
核心原则
每个任务派全新子代理 + 两阶段审查（规范→质量）= 高质量、快迭代。
WorkBuddy 子代理调度模式
使用 WorkBuddy 的 Agent 工具派发子代理，配合 TaskCreate/TaskUpdate 管理任务状态。
GOAL: [一句话——什么结果]
CONTEXT: [计划文件路径 + 相关背景]
FILES: [精确的文件路径]
CONSTRAINTS: [TDD 强制、不扩范围、无不测试的代码]
VERIFY: [测试命令 + 预期输出]
TASK: [粘贴计划文档中的完整任务文本]
逐任务循环
对计划中的每个任务：
-
派发实现者子代理 (Agent general-purpose)
- 包含：完整任务文本、计划文件路径、TDD 约束
- 等待完成通知
-
派发规范审查子代理
- 包含：实现了什么、计划要求、git diff
- 必须确认：代码精确匹配规格
- 有遗漏 → 重新派实现者修复
-
派发代码质量审查子代理
- 包含：git diff、实现描述
- 必须批准：干净代码、无死代码、DRY、YAGNI
- 有问题 → 派实现者修复，重新审查
-
标记任务完成，下一个任务
全部任务完成后
- 派发最终总体审查子代理（完整 diff、所有任务）
- 修复发现的严重/重要问题
- 移交
finishing-a-development-branch
实现者子代理提示模板
你是实现一个编码任务的子代理。严格遵循 TDD。
计划文件: [路径]
任务: [任务 N 文本]
约束:
- 先写失败测试。运行。确认失败。再实现。
- 只做最小实现 — YAGNI
- 每个绿色测试后提交: git add <files> && git commit -m "..."
- 不要改任务范围外的文件
- 不要加任务中没有的功能
验证:
- 运行: [测试命令]
- 预期: [预期输出]
完成后报告: 实现了什么、测试结果、提交 SHA。
规范审查子代理提示模板
你是做规范合规审查的子代理。
计划文件: [路径]
正在审查的任务: [任务 N 文本]
GIT 范围: [base_sha..head_sha]
只审查实现是否匹配规格。
报告:
- PASS 或 FAIL
- 任何规格遗漏（规格要求但未实现的）
- 不要评论代码风格或质量
代码质量审查子代理提示模板
你是做代码质量审查的子代理（不审查规范合规）。
GIT 范围: [base_sha..head_sha]
描述: [实现了什么]
审查:
- DRY 违反
- 死代码
- YAGNI 违反（不必要的功能）
- 命名问题
- 缺少错误处理
严重程度: 严重 / 重要 / 次要
报告: 批准，或按严重程度列出问题。
审查严重程度处理
| 严重程度 | 行动 |
|---|---|
| 严重 | 先修复再继续 — 阻塞后续任务 |
| 重要 | 先修复再继续 |
| 次要 | 记录，稍后处理 |
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.
- 7d ago First seen · 116 lines · 59 tokens per session scan A 3bb6c9138691
subagent-driven-development is a skill published in the GitHub repository yinqd3/workbuddy-skills (6 stars, last pushed 3mo ago), licensed MIT. It adds 59 tokens to every session and 885 once invoked, about $0.0003 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 skills, from other repositories
results-report
A workflow for turning completed experiment analyses into a structured research report with findings, limitations, failures, and next steps.
math-unicode
Use whenever you need to express mathematical notation — equations, filters, set-builder, statistics, calculus, logic, ratios, drops, counts. Emit Unicode math glyphs INLINE; never wrap in $…$, \(...\), or $$...$$. Terminal coding agents (Claude Code, Codex CLI, and others) do not render LaTeX, so raw delimiters…
obsidian-markdown
Obsidian Flavored Markdown syntax reference — wikilinks, embeds, callouts, properties/frontmatter, tags, comments, block IDs. Use when creating or editing .md files in an Obsidian vault, when linking or embedding notes, when writing callouts or note frontmatter, or when the user mentions wikilinks, backlinks, block…
obsidian-docs
Create comprehensive technical documentation following Obsidian conventions with bidirectional linking, proper folder structure, templates, and developer-focused content. Use when creating documentation, READMEs, wikis, knowledge bases, ADRs, runbooks, or any technical writing. Triggers on: documentation, docs…
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
skill-creator
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.