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 rules/yudefine/nuxt-supabase-starter/worktree-default.commit-ceremonygit clone --depth 1 https://github.com/YuDefine/nuxt-supabase-starterWrote 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/rules/yudefine/nuxt-supabase-starter/worktree-default.commit-ceremony)<a href="https://agentmods.dev/rules/yudefine/nuxt-supabase-starter/worktree-default.commit-ceremony"><img src="https://agentmods.dev/badge/rules/yudefine/nuxt-supabase-starter/worktree-default.commit-ceremony.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.00000 | $0.03554 |
| Opus 5 | $0.00000 | $0.01777 |
| Sonnet 5 | $0.00000 | $0.00711 |
| Haiku 4.5 | $0.00000 | $0.00355 |
Grade A, and why
worktree-default.commit-ceremony 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 today.
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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Path-scoped detail of [[worktree-default]] §5 / §5.5 / §6。核心 always-load 規約在母檔 worktree-default.md。
§5 Commit 階段：subagent commit → archive 吸收 → user /commit
v3 atomic landing model（取代 v2 「/wt 返回時 squash」）：
/wt 返回時保留已 commit 的 worktree／branch。OPSX archive 在實作樹驗證並封存目前 revision；主持者提交 bookkeeping 後，序列合回 main 並立即限定路徑 commit。驗收、歸檔、落地與部署各自有證據。
為什麼從 v2 改 v3
v3 atomic landing 解這些：main 永遠 deployable；多 session 平行不污染 main（每條 worktree 各自保留到 archive）；一個 ceremony land 全部；人工檢查 Gate 與 archive gate 對齊為同一道進 main 關卡。
Mechanic
Codex 派工規約（細則見 [[agent-routing.pi-watch-protocol]] § Commit Authorization）：codex 可在 worktree 內 commit，但 MUST 遵守：一 phase 一 commit、message 強制 🧹 chore: wt <change>-phase-<N> — <short>、不繞 hook（禁止 --no-verify）、selective stage（禁止 git add -A）、commit 前自跑 drift + scope check、仍禁止 git push / 中途 git stash / --amend / /commit / /spectra-commit。主線收到完工通知後 MUST 驗 commit 邊界對齊 phase + format、double-check drift / scope（發現 → git -C <wt> reset --soft main 重派）、跑 typecheck / test。
本段「Subagent 在 worktree commit」對 Claude subagent 與 codex 都適用（規約相同）；差別只在 subject 後綴：Claude subagent 用 🧹 chore: wt <slug> — <free-form>，codex 強制 phase 格式以利主線對齊。
- Subagent 在 worktree 內 commit（
/wtprompt template 強制）：git add -- <scoped file>selective stage（禁止git add -A） +git commit -m "🧹 chore: wt <slug> — <short>"，可多 commit，pre-commit / commit-msg hook 必跑。NEVER：git push//commit//spectra-commit。 /wt返回時：不 squash，不 cleanup。worktree + branch 保留，主線只報告 status。- OPSX 驗證與歸檔：在實作 worktree 依
/opsx的references/execution.md回讀目前 revision、證據與人工 gate，再執行 archive；未過的 gate 保持阻擋。 - 提交封存結果：在該 worktree 限定路徑 commit 實作與 bookkeeping，檢查 clean、scope 及內容。archive 不自動 merge-back。
- 主持者序列落地：先同步 main、檢查並行 WIP 與 merge-back dry-run；放行後只合一棵樹，立刻依
/commit在 main 限定路徑 commit，驗每個檔的內容與 scope，再處理下一棵樹。既有授權不足時保留 worktree 與可審查結果，等待具體 gate。
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.
- today Changed 95c086515374
- 2d ago First seen · 110 lines · 0 tokens per session scan A 6842b6bb5f0d
worktree-default.commit-ceremony is a cursor rule published in the GitHub repository YuDefine/nuxt-supabase-starter (45 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,554 tokens. 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-09-03.
Other cursor rules, from other repositories
workflow
Development workflow and commit practices.
cmd-build
Implement the next task incrementally — build, test, verify, commit.
speckit_speckit.git.commit
Proxy for the speckit.git.commit workflow.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.