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 midFang/ai-agent-skills-workflow --skill bugfix-donegit clone --depth 1 https://github.com/midFang/ai-agent-skills-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/midfang/ai-agent-skills-workflow/bugfix-done)<a href="https://agentmods.dev/skills/midfang/ai-agent-skills-workflow/bugfix-done"><img src="https://agentmods.dev/badge/skills/midfang/ai-agent-skills-workflow/bugfix-done.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.00135 | $0.01700 |
| Opus 5 | $0.00068 | $0.00850 |
| Sonnet 5 | $0.00027 | $0.00340 |
| Haiku 4.5 | $0.00014 | $0.00170 |
Grade A, and why
bugfix-done 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bugfix Done
目的
处理 bug 修复流程的后半段：
用户人工验证通过
-> 标记 human_verified
-> 合并到用户指定目标分支
-> 标记 merged
-> 构建并安装目标分支 APK
-> 等用户做合并后/目标分支验证
-> 标记 integration_verified
-> 删除 worktree
-> 标记 worktree_removed
这个 skill 不负责修 bug，不负责构建首次待验证 APK，不负责首次安装。那些由 $bugfix-worktree 完成。本 skill 负责合并成功后的目标分支 APK 构建和安装，供用户做合并后验证。
输入
需要：
bug_id，例如BUG-001- issues CSV 路径，或能从业务项目
issues/<版本>/bug_batch.csv唯一定位 - 目标分支，仅在“合并”阶段必须提供，例如
main、develop、release/x.y
如果用户说“验证通过，合并”，但没有说目标分支，必须先问：
要把 BUG-xxx 合并到哪个目标分支？
不要猜目标分支。
阶段 A：人工验证通过并合并
触发示例：
$bugfix-done BUG-001 验证通过，合并到 main
步骤：
- 读取 issues CSV 中的 bug 行。
- 确认
worktree_path、branch、commit、task_file存在。 - 更新 CSV：
状态=human_verifiedhuman_verify_result=passhuman_verify_note记录用户确认和时间
- 更新
issues/<版本>/tasks/<bug_id>-TASK.md的“用户人工验证”小节。 - 合并前检查：
- bug worktree 没有未提交改动
- 目标分支由用户明确给出
- 执行合并的仓库不能有业务代码/配置类未提交改动
issues/**/*.md、issues/**/*.csv、features/**/*.md、features/**/*.csv、features/**/*.json这类流程文件允许存在改动，不应阻止合并- 如果主仓库因为目标分支已 checkout、工作区限制或其它原因不适合直接合并，可以创建干净的临时集成 worktree 来执行合并
- 切到目标分支。
- 默认执行非 fast-forward merge：
- merge commit message 使用：
Merge <bug_id> fix: <中文问题描述或修复内容> - 中文描述优先取 CSV 的
人工确认描述，其次取标题或问题描述，过长时压缩成一句话。 - 示例：
git merge --no-ff -m "Merge BUG-013 fix: 等待接收设备同意超时只显示一个提示弹窗" <bug-branch>
- merge commit message 使用：
- 合并成功后更新 CSV：
状态=mergedtarget_branch备注记录 merge commit
- 更新 TASK，记录目标分支、merge commit、合并结果。
- 在目标分支构建合并后的 APK：
- 优先使用项目已有 Android 构建命令，例如
./gradlew :app:assembleDebug或./gradlew assembleDebug - 将生成的 APK 复制到
issues/<版本>/apks/<bug_id>-merged.apk
- 安装合并后的 APK：
- 运行
adb devices - 如果有多个设备，询问用户选择 serial
- 执行
adb install -r issues/<版本>/apks/<bug_id>-merged.apk - 可做基础 smoke test，例如启动应用、观察进程、查看 logcat 是否有明显崩溃
- 更新 CSV/TASK：
备注记录合并后 APK 路径、安装设备、安装结果和 smoke test 摘要- TASK 记录“合并后验证待确认”
- 合并后不要删除 worktree。提示用户在目标分支/集成包上再次验证。
如果合并后构建或安装失败：
- 不要删除 worktree。
- 不要回滚已经成功的 merge，除非用户明确要求。
- 保持
状态=merged或设置状态=blocked，根据失败是否阻断用户验证判断。 blocked_reason=integration_failed或更具体的build_failed/device_unavailable。- 在 TASK 记录失败命令、错误摘要和下一步。
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 150 lines · 135 tokens per session scan A e1cb3dcd6eed
bugfix-done is a skill published in the GitHub repository midFang/ai-agent-skills-workflow (2 stars, last pushed 2mo ago), licensed MIT. It adds 135 tokens to every session and 1,700 once invoked, about $0.0007 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
agent-merge-conflict-arbiter
Neutral arbiter for merge conflicts between two agents.
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
bisect
Bisect regressions or broken builds in the Chromium repository using deterministic binary search, checking out midpoint commits, syncing dependencies with gclient sync, compiling the target with autoninja, and querying the user for test results until the culprit commit is isolated.
mantis-critic
Assesses the production viability of findings, filtering out debug-only features and assertion traps. Use when findings have been validated and you need to confirm they are triggerable in production release builds (with assertions disabled). Don't use for writing reproduction scripts or patches.
hotpath_bump
Bump the hotpath version number across the workspace and related files. Updates crate versions in Cargo.toml files (exact patch version) and version references in the backend middleware, hotpathinit skill, and README (major.minor only). Use when the user wants to bump, bump the version, or release a new hotpath…
comet-github-issue-fix
A workflow for fixing a confirmed Comet-related GitHub issue or review blocker within an isolated scope. It covers matching the work to the relevant workflow, testing the change, checking runtime results, and preparing a careful handoff.