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 agentmods add skills/ccdawn/codex-skills/briefbound-thread-coordinationnpx skills add CCDawn/codex-skills --skill briefbound-thread-coordinationgit clone --depth 1 https://github.com/CCDawn/codex-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/ccdawn/codex-skills/briefbound-thread-coordination)<a href="https://agentmods.dev/skills/ccdawn/codex-skills/briefbound-thread-coordination"><img src="https://agentmods.dev/badge/skills/ccdawn/codex-skills/briefbound-thread-coordination.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 | $0.00058 | $0.01386 |
| Opus 5 | $0.00029 | $0.00693 |
| Sonnet 5 | $0.00012 | $0.00277 |
| Haiku 4.5 | $0.00006 | $0.00139 |
Grade A, and why
briefbound-thread-coordination 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 5d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Briefbound Thread Coordination
目标
以 registry/thread 协调 scope、冲突和合并；Git 为事实源。
Briefbound task contract
- Context Boundary: 项目/thread/branch/worktree/scope/claim/coordination，以及共享 runtime 的 PID、listener、data root 和 owner。
- Output Contract: ownership、决定、验证、恢复债务。
- Allowed Action: 使用
read_thread、send_message_to_thread、只读进程探针与agent_coordination.py；不停止未知 owner 进程，创建/归档或远程 Git 需授权。 - Success Evidence: registry revision、thread 回执、Git/测试及协调闭环。
- Stop Condition: thread 不明、owner 争议、暂停未确认、状态漂移或未授权。
- Route Out: 原 owner、
briefbound-autonomous-collaboration-loop、briefbound-multi-agent-orchestration、briefbound-pr-review、briefbound-development-cleanup、briefbound-project-memory、briefbound-router或 BLOCKED。
统一调用契约
- 只处理 Briefbound task contract；不匹配时回具体 owner。
- 用户可见内容默认中文；只报产出、证据和风险；Route Out 仅以 Briefbound task contract 为准；末行写
下一步建议: <一个具体动作>。
接入与所有权
preflight 传 --write-kind development|mechanical|integration：根 main/master 开发返回 ISOLATION_REQUIRED，集成需 claim + clean；其余按 CLEAR/PEERS_NO_OVERLAP 或 OVERLAP 分诊，只 claim 最小 scope。
owner 顺序：用户指定 > 有效 claim/registry > 更早 owner。非 owner 停止自身冲突写入，不要求既有 owner 暂停；争议面只读。
文件/集成 owner 分开。MERGE_READY 时读 references/integration-ownership.md，按 claim 认领或退回交付者。
共享进程、listener 或 data root 冲突时，读取 references/proactive-collaboration.md 的“运行进程归属”；端口不同不等于数据隔离。确认 owner 后，运行中仲裁仍由本 skill 负责，已知本任务进程的安全停止与释放转 briefbound-development-cleanup。
主动协作
消息投递或协作时读 references/proactive-collaboration.md，不转移 owner。
skill 只提供协调原语。持续互助交 briefbound-multi-agent-orchestration；自动闭环由 briefbound-autonomous-collaboration-loop 驱动并继承恢复债务。不得建立主从关系。
新会话有收益才询问是否创建；未授权不创建，也不停止当前工作。
冲突恢复
Silent Conflict Triage 核验 claim、真实写入和替代工作；优先 SELF_NARROWED / CONTINUE_NON_CONFLICTING / WAIT_SILENTLY。
需共同决定时为 DISCUSSION_REQUIRED：复用 open coordination，否则发送含双方身份、原任务和 Reply To 的 DISCUSSION_REQUEST。各方回复 position；Coordination Owner 汇总 proposal，ACK 回复其 thread；收齐后 resolve 并广播 final，final 不索要回复。期间继续各自安全工作。
继续执行会立即覆盖/回归、无法拆分且协商不能避免时才为 PAUSE_REQUIRED：升级 conflict，发送一次 CONFLICT_PAUSE_REQUEST。PAUSE_REQUEST 不等于 PAUSED，确认前不写冲突面。
What ships with it
3 files 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.
- 5d ago First seen · 78 lines · 58 tokens per session scan A c075857841a6
briefbound-thread-coordination is a skill published in the GitHub repository CCDawn/codex-skills (4 stars, last pushed 23d ago), licensed MIT. It adds 58 tokens to every session and 1,386 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
chinese-git-workflow
国内 Git 平台配置参考——Gitee、Coding.net、极狐 GitLab、CNB 的 SSH/HTTPS/凭据/CI 接入差异与镜像同步配置。仅在用户显式 /chinese-git-workflow 时调用，不要根据上下文自动触发。.
chinese-code-review
中文 review 沟通参考——话术模板、分级标注（必须修复/建议修改/仅供参考）、国内团队常见反模式应对。仅在用户显式 /chinese-code-review 时调用，不要根据上下文自动触发。.
chinese-commit-conventions
中文 commit 与 changelog 配置参考——Conventional Commits 中文适配、commitlint/husky/commitizen 中文模板、conventional-changelog 中文配置。仅在用户显式 /chinese-commit-conventions 时调用，不要根据上下文自动触发。.
chinese-documentation
中文文档排版参考——中英文空格、全半角标点、术语保留、链接格式、中文文案排版指北约定。仅在用户显式 /chinese-documentation 时调用，不要根据上下文自动触发。.
systematic-debugging
Skill "systematic-debugging" from jnMetaCode/superpowers-zh, covering 系统化调试, 概述, 铁律, 何时使用 and 四个阶段.
mcp-builder
MCP 服务器构建方法论 — 系统化构建生产级 MCP 工具，让 AI 助手连接外部能力.