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 executing-plansgit 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/executing-plans)<a href="https://agentmods.dev/skills/yinqd3/workbuddy-skills/executing-plans"><img src="https://agentmods.dev/badge/skills/yinqd3/workbuddy-skills/executing-plans.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.00055 | $0.00468 |
| Opus 5 | $0.00028 | $0.00234 |
| Sonnet 5 | $0.00011 | $0.00094 |
| Haiku 4.5 | $0.00006 | $0.00047 |
Grade A, and why
executing-plans 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 6d 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
执行计划（内联模式）
概述
在同一个会话中逐任务执行实现计划。适合中小型项目或不需要并行子代理的场景。
开始时声明： "我将用 executing-plans 技能逐任务执行实现计划。"
执行流程
任务 1 → 检查点审查 → 任务 2 → 检查点审查 → ... → 最终验证
逐任务执行规则
-
使用 TaskCreate/TaskUpdate 跟踪进度
- 每个计划任务映射为一个 WorkBuddy 任务
- 开始前标记
in_progress，完成后标记completed
-
每个任务遵循 TDD
- 先写失败测试 → 验证失败 → 最小编码 → 验证通过 → 提交
-
按检查点分批
- 每 3-5 个任务后暂停审查
- 确认规范合规 + 代码质量
检查点审查清单
每批任务完成后：
- 所有测试通过
- 实现匹配计划中的规格
- 无死代码
- DRY（无重复）
- YAGNI（无过度工程）
- 所有变更已提交
错误处理
执行过程中遇到错误：
- 暂停当前任务
- 触发
systematic-debugging进行根因调查 - 修复后继续
- 不要跳过有问题的任务
完成后
- 运行完整测试套件
- 移交
verification-before-completion做最终验证 - 通过后移交
finishing-a-development-branch
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.
- 6d ago First seen · 57 lines · 55 tokens per session scan A 549c5c402780
executing-plans is a skill published in the GitHub repository yinqd3/workbuddy-skills (6 stars, last pushed 3mo ago), licensed MIT. It adds 55 tokens to every session and 468 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.