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 verification-before-completiongit 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/verification-before-completion)<a href="https://agentmods.dev/skills/yinqd3/workbuddy-skills/verification-before-completion"><img src="https://agentmods.dev/badge/skills/yinqd3/workbuddy-skills/verification-before-completion/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/yinqd3/workbuddy-skills/verification-before-completion"><img src="https://agentmods.dev/badge/skills/yinqd3/workbuddy-skills/verification-before-completion.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.00053 | $0.00555 |
| Opus 5 | $0.00026 | $0.00278 |
| Sonnet 5 | $0.00011 | $0.00111 |
| Haiku 4.5 | $0.00005 | $0.00056 |
Grade A, and why
verification-before-completion 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 9d 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
完成前验证
概述
在声明"完成"之前，必须逐项过这个验证清单。任何一项不通过 = 未完成。
开始时声明： "我将用 verification-before-completion 技能做最终验证。"
验证清单
1. 测试验证
- 所有测试通过（全量套件，非仅新增）
- 新增测试覆盖所有新功能
- 边界情况和错误路径有测试
- 测试用真实代码（mock 只在不可避时）
# Python
pytest -q --cov
# Node/TS
pnpm test -- --coverage
2. 规范合规
- 所有规格要求已实现
- 没有规格外的功能（YAGNI）
- 行为和设计文档描述一致
3. 代码质量
- 无死代码
- 无重复代码（DRY）
- 命名清晰
- 错误处理完整
- Lint 干净
# Python
ruff check .
# Node/TS
npx eslint .
4. 文件整洁
- 无临时文件、调试日志
- 无注释掉的代码
- 无
console.log/print遗留
5. 文档同步
- 相关文档已更新
- 如有 README，已反映变更
- 如有 API 变更，已记录
6. Git 状态
- 所有变更已提交
- 提交信息清晰
- 无遗漏的未跟踪文件
git status
git log --oneline -5
不通过的处理
任何一项不通过：
- 列出问题清单
- 逐项修复
- 重新运行完整验证
- 全部通过后才说"完成"
通过后
- 移交
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.
- 9d ago First seen · 82 lines · 53 tokens per session scan A 13a140856258
verification-before-completion is a skill published in the GitHub repository yinqd3/workbuddy-skills (6 stars, last pushed 3mo ago), licensed MIT. It adds 53 tokens to every session and 555 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
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code.
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
verification-loop
This skill should be used when the user asks to "verify code", "run verification", "check quality", "validate changes", or before creating a PR. Provides comprehensive verification including build, type check, lint, tests, security scan, and diff review.
asc-shots-pipeline
Orchestrate iOS screenshot automation with xcodebuild/simctl for build-run, AXe for UI actions, JSON settings and plan files, Koubou-based framing (asc screenshots frame), and screenshot upload (asc screenshots upload). Use when users ask for automated screenshot capture, AXe-driven simulator flows, frame composition…