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 zhuanggenhua/BoardGame --skill merge-decision-packagegit clone --depth 1 https://github.com/zhuanggenhua/BoardGameWrote 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/zhuanggenhua/boardgame/merge-decision-package)<a href="https://agentmods.dev/skills/zhuanggenhua/boardgame/merge-decision-package"><img src="https://agentmods.dev/badge/skills/zhuanggenhua/boardgame/merge-decision-package/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/zhuanggenhua/boardgame/merge-decision-package"><img src="https://agentmods.dev/badge/skills/zhuanggenhua/boardgame/merge-decision-package.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00045 | $0.01477 |
| Opus 5 | $0.00023 | $0.00739 |
| Sonnet 5 | $0.00009 | $0.00295 |
| Haiku 4.5 | $0.00005 | $0.00148 |
Grade A, and why
merge-decision-package 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 12d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
保留与合并决策包
概览
把“有两边内容要不要保留/合并”的混乱问题，压成普通人能直接判断的决策包。默认先说明哪些能全保留、哪些只是正式入口不能双生效，再给一句用户可直接回复的推荐方案。
规范来源与职责边界
- 本 skill 是
workflow：只负责生成给用户看的保留/合并裁决包。 - 分支 / worktree 目标锁定和删改影响标准，以
.spec/knowledge/standards/worktree-branch-target-lock.md为canonical-source。 - PR / 分支合并、普通提交和推送不由本 skill 执行；本 skill 只生成决策包。
- 本 skill 不执行合并、不删除分支、不移动文件；它只把证据转成用户能判断的决策说明。
先决条件
开始前先锁定四件事：
当前真相源- 哪套截图、artifact、已提交版本、规则书或已认可实现是真正基线。
实施落点- 当前实际改的是哪棵 worktree / 分支 / 工作区。
候选范围- 到底是哪几批内容在争夺正式入口，哪些只是过程材料。
用户当前真正要决定的问题- 是选正式实现、还是决定删不删候选、还是只要一份能看懂的判断说明。
以上四项有一项没锁定，就先补证据，不要先写结论。
决策分类
先把内容归到下面四类，再决定是否需要用户拍板：
正式实现单选- 同一路由、同一运行时入口、同一正式导出、同一正式测试真相，只能先认一边。
候选实现可保留- 暂时不翻正，但可以继续留在 worktree、分支或工作区里，后续再审。
过程材料双保留- 截图、evidence、审计文档、草稿、设计说明、比较文档可以一起留。
独立小项可单独吸收- 不直接改正式 UI/交互真相的小项，可以脱离主冲突单独收口。
只要还有一种“先都保留、暂不删除、只冻结正式入口”的路径，就必须先告诉用户，不能直接问“删哪边”。
先自己裁决，不要滥问用户
若现有证据已经足以单边裁决，就直接做：
- 真相源已被用户明确认可。
- 某一边只是过程文档或历史候选，不会影响正式入口。
- 某几个小项已经证明与正式 UI 基线不冲突。
只有在下面情况才进入“需要用户拍板”：
- 正式实现真要换基线。
- 两套正式候选都自洽，但证据不足以单边淘汰。
- 接受某一边就会连带切换文案合同、验证合同或运行入口。
生成决策包的固定顺序
面向用户的正文固定按这个顺序写：
一句话总结- 先说当前不是在删哪边，而是在决定正式版本先认哪边。
先回答三件事- 这是不是只能二选一。
- 哪些部分可以全部保留。
- 哪些部分只是同一正式入口不能双生效。
用户现在只需要决定的一句话- 给出推荐句，用户可以直接回复“同意/不同意”。
为什么推荐这个- 用现实影响解释，不先上文件名。
如果选另一边会发生什么- 直接翻译成产品后果、UI 后果、验收后果。
最后才放技术附录- 批次、文件、证据路径放最后，不要放在开头。
决策包必须回答的最小问题
无论场景如何，正文里至少要明确回答：
- 现在是不是所有内容都只能二选一。
- 如果不是，哪些能保留，分别怎么保留。
- 当前最低风险路径是不是“先不删任何一边，只冻结正式入口”。
- 用户真正需要决定的，究竟是不是只有“正式版本先认哪一边”。
- 我推荐哪一边，为什么。
禁止行为
- 不要把“同路径有 diff”直接表述成“只能删一边”。
- 不要把正式实现、候选实现、过程材料、旧草稿压扁成一个二选一问题。
- 不要先报 11 个文件、4 个批次，再让用户自己翻译现实含义。
- 不要让用户先看代码才能判断。
- 不要在还存在“全部先保留”的低风险路径时，直接推动删除。
大任务与 OpenSpec
如果这次决策会引出新的长期流程、跨模块治理变更、或后续要按正式方案持续实施一整批任务，先回到 openspec/AGENTS.md 判断是否要补 change proposal / tasks，把大任务拆成小任务后再继续实施。这个 skill 负责“把决策说清楚”，不替代 OpenSpec 的长期规划职责。
输出模板
# <主题> 决策包
## 一句话结论
<先说当前推荐，不先说文件名>
## 先回答三件事
1. 这是不是只能二选一：<是/不是，为什么>
2. 现在可以全部保留的：<候选实现 / evidence / 审计 / 说明 ...>
3. 现在不能两边同时生效的：<正式入口 / 正式 UI / 正式合同 ...>
## 你现在只需要决定的一句话
<给出一条用户可直接回复“同意/不同意”的推荐句>
## 为什么我推荐这个
- <现实影响 1>
- <现实影响 2>
- <现实影响 3>
## 如果改选另一边，会发生什么
- <直接说产品后果>
## 附录：技术映射
- <批次 -> 文件 -> 证据路径>
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.
- 12d ago First seen · 131 lines · 45 tokens per session scan A 3e0124155798
merge-decision-package is a skill published in the GitHub repository zhuanggenhua/BoardGame (23 stars, last pushed yesterday), licensed MIT. It adds 45 tokens to every session and 1,477 once invoked, about $0.0002 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-30.
Other skills, from other repositories
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…