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.
git clone --depth 1 https://github.com/zyx379/zoehis_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/rules/zyx379/zoehis_workflow/zoehis-git-branch)<a href="https://agentmods.dev/rules/zyx379/zoehis_workflow/zoehis-git-branch"><img src="https://agentmods.dev/badge/rules/zyx379/zoehis_workflow/zoehis-git-branch/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/rules/zyx379/zoehis_workflow/zoehis-git-branch"><img src="https://agentmods.dev/badge/rules/zyx379/zoehis_workflow/zoehis-git-branch.svg" alt="Reviewed on agentmods" width="80" 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.01069 | $0.01069 |
| Opus 5.5 | $0.00428 | $0.00428 |
| Sonnet 5.5 | $0.00214 | $0.00214 |
| Haiku 4.5 | $0.00107 | $0.00107 |
Grade A, and why
zoehis-git-branch 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 2mo 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ZOEHIS Git 规范
工作区为 10 个独立 Git 子仓库（根目录无 Git）。每个将改动的子仓库单独操作。完整步骤见 docs/workflow.md Step 10。
分支策略
- master：所有功能开发在此分支；改前
git checkout master && git pull origin master - release-*：项目发布分支；禁止在 release 上直接改功能，仅 merge master
- 仅解决冲突时可在项目分支操作，完成后 切回 master
交付期顺序（审查确认后）
1. push master
git add <files>
git commit -m "[禅道号/需求号]【项目名称】需求标题"
git push origin master
Commit 正文约束（硬约束）：
- 禁止在 commit message 中出现
Co-authored-by: Cursor或[email protected]等 Agent/IDE 署名行 - 仅保留一行标题：
[禅道号/需求号]【项目名称】需求标题，不要追加 Co-authored-by、Made-with-Cursor 等 trailer - 若环境自动注入 Co-authored-by，提交前用
git log -1 --format=full核对；含上述字样则--amend去掉后再 push
2. 合并到项目分支（先 master，再按 commit 关键词）
commit message 匹配关键词时，将 master merge 进 对应项目分支：
| 提交关键词 | 项目分支 |
|---|---|
【漳州市医院】 |
release-1.168 |
【漳州二院】 |
release-1.166 |
匹配时 优先最长关键词。
无医院关键词（未知项目，如 commit 仅含 [******] 占位）： 跳过步骤 2 merge；步骤 3 在 master 打 release-0.0.{max+1} tag（全仓 release-0.0.* 最大序号 +1）触发 CI 编译。
git checkout <项目分支>
git pull origin <项目分支>
git merge master
git push origin <项目分支>
git checkout master
无关键词匹配且用户未指定分支 → 未知项目：只做步骤 1 push master，不 merge release-1.166/1.168；步骤 3 在 master 打 release-0.0.{max+1} tag。
onelink-web-cis-common 例外： CIS 公共 npm 包，无 release-* 与 tag；始终只做步骤 1（push master），不 merge、不打 tag，不参与项目分支 CI 编译。
3. Tag（已知医院：项目分支 max+1；未知项目：master 上 release-0.0.max+1）
已知医院 — 在 项目分支（非 master）上：
git checkout <项目分支>
git pull origin <项目分支>
# 取该分支最大 tag，版本 +1（如 release-1.168.31 → release-1.168.32）
git tag <新版本号>
git push origin <新版本号>
git checkout master
未知项目 — 在 master 上（commit 无医院关键词时）：
git checkout master
git pull origin master
# 全仓 release-0.0.* 最大序号 +1（如 release-0.0.1375 → release-0.0.1376）
git tag release-0.0.<序号>
git push origin release-0.0.<序号>
Agent 两阶段
| 阶段 | 允许 | 禁止 |
|---|---|---|
| 实现期 | 改代码；master pull | commit / push / merge / tag |
| 交付期（人审确认后） | 10.1→10.2→10.3 按 docs/workflow.md |
未经确认不得 git |
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.
- 2mo ago First seen · 94 lines · 1,069 tokens per session scan A c533ce6771e8
zoehis-git-branch is a cursor rule published in the GitHub repository zyx379/zoehis_workflow (2 stars, last pushed 3mo ago), licensed MIT. It adds 1,069 tokens to every session, about $0.0043 per session on Opus 5.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 cursor rules, from other repositories
github-workflow
GitHub invariants — standard flow on listed use cases; no issue spam; tick linked checklists before merge.
git
Git rules. Conventional commits, atomic staging, no force push.
release-ts-sdk
Release @aptos-labs/ts-sdk or @aptos-labs/confidential-asset — version bump, changelog stamp, release PR, then tag + GitHub Release that triggers NPM publish.
40-git-safety
Git safety rule for branches, commits, pushes, and destructive Git commands.
git-master
Git operations — clean commits, PR prep, conflict resolution, change summaries.
git-workflow
Git branching and PR workflow.