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 commands/seekers2001/docs-governance/governance-syncgit clone --depth 1 https://github.com/Seekers2001/docs-governanceWhat 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.00043 | $0.00484 |
| Opus 5 | $0.00022 | $0.00242 |
| Sonnet 5 | $0.00009 | $0.00097 |
| Haiku 4.5 | $0.00004 | $0.00048 |
Grade A, and why
governance-sync 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 2d 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
调用 docs-governor 子 agent，对当前工作目录做一次阶段收尾同步。
用户参数（可选）：$ARGUMENTS
- 不带参数：根据当前项目状态、最近变更和治理文档做查漏补缺。
- 带一句话：把这句话作为本阶段完成事项，例如
完成答题点亮链路。 - 带
contract：重点检查本阶段是否需要同步CONTRACT.md。
执行要求：
- 先读
living-docs-governanceskill 和references/governance-sync-matrix.md。 - 盘点本阶段变化：会话上下文、最近修改文件、项目结构、已有四件套。
- 按矩阵判断应同步哪些文件：
- 结构变化 →
CLAUDE_MAP.md - 健康/风险/待删 →
PROJECT_STATUS.md - 长期硬规则 →
CLAUDE.md - 有意义事件 →
PROJECT_LOG.md - 接口字段变化 →
CONTRACT.md - 领域术语变化 →
CONTEXT.md（若已启用） - 难回退技术决策 →
docs/adr/ - 成功标准与证据 → Spec/Issue +
TESTS.md - 模块行为与下游命令 →
REGRESSION.md
- 结构变化 →
- 能确定的当前真相直接增量更新；不确定的列入“待用户确认”，不要编。
- 对照
change-impact的计划影响与实际 diff，报告超范围改动、未验证项和临时兼容逻辑。 PROJECT_LOG.md只追加；只有超过 200 条且用户确认时，才用确定性脚本原样归档。- 交付时列出：实际改了哪些文档、每份为什么改、哪些没改、哪些需要人工确认。
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.
- 2d ago First seen · 31 lines · 43 tokens per session scan A 92fe8b33bc43
governance-sync is a command published in the GitHub repository Seekers2001/docs-governance (11 stars, last pushed 20d ago), licensed MIT. It adds 43 tokens to every session and 484 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-31.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
project-recap
Generate a visual project recap for context switching.
speckit.taskstoissues
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
ado-pull
Pull latest changes from Azure DevOps (like git pull). Supports increment, project, or full living docs sync.
issue-amend
Re-snapshot the active issue's scope from the spec, clear verified and reviewed receipts, and record the change as a permanent amendment.
dispatch-worker
Run one in-session-agent Worker tick (RFC-0041 §4.3.1).