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/WangTingYeYe/llm-agent-studyWrote 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/wangtingyeye/llm-agent-study/gitflow)<a href="https://agentmods.dev/rules/wangtingyeye/llm-agent-study/gitflow"><img src="https://agentmods.dev/badge/rules/wangtingyeye/llm-agent-study/gitflow/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/wangtingyeye/llm-agent-study/gitflow"><img src="https://agentmods.dev/badge/rules/wangtingyeye/llm-agent-study/gitflow.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.00000 | $0.00731 |
| Opus 5.5 | $0.00000 | $0.00292 |
| Sonnet 5.5 | $0.00000 | $0.00146 |
| Haiku 4.5 | $0.00000 | $0.00073 |
Grade A, and why
gitflow 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 1mo 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
Gitflow工作流规则
主分支
main（或master）
- 包含生产就绪代码
- 永远不要直接提交到main分支
- 只接受来自以下分支的合并：
- hotfix/* 分支
- release/* 分支
- 每次合并后必须使用版本号标记
develop
- 主开发分支
- 包含最新交付的开发变更
- 功能分支的源分支
- 永远不要直接提交到develop分支
支持分支
feature/*
- 从develop分支创建
- 合并回：develop
- 命名约定：feature/[issue-id]-描述性名称
- 示例：feature/123-user-authentication
- 创建PR前必须与develop分支保持同步
- 合并后删除
release/*
- 从develop分支创建
- 合并回：
- main
- develop
- 命名约定：release/vX.Y.Z
- 示例：release/v1.2.0
- 仅进行bug修复、文档编写及与发布相关的任务
- 不添加新功能
- 合并后删除
hotfix/*
- 从main分支创建
- 合并回：
- main
- develop
- 命名约定：hotfix/vX.Y.Z
- 示例：hotfix/v1.2.1
- 仅用于紧急生产环境修复
- 合并后删除
提交信息
- 格式：
type(scope): description - 类型：
- feat: 新功能
- fix: Bug修复
- docs: 文档变更
- style: 格式调整、缺失分号等
- refactor: 代码重构
- test: 添加测试
- chore: 维护任务
版本控制
语义化版本
- MAJOR版本用于不兼容的API变更
- MINOR版本用于向后兼容的功能性变更
- PATCH版本用于向后兼容的bug修复
Pull Request规则
- 所有变更必须通过Pull Request进行
- 所需批准：至少1个
- CI检查必须通过
- 不允许直接提交到受保护分支（main, develop）
- 合并前分支必须保持最新
- 合并后删除分支
分支保护规则
main和develop
- 要求Pull Request审核
- 要求状态检查通过
- 要求分支保持最新
- 限制规则包括管理员
- 禁止强制推送
- 禁止删除
发布流程
- 从develop创建release分支
- 更新版本号
- 修复任何与发布相关的问题
- 创建PR到main
- 合并到main后：
- 标记发布
- 合并回develop
- 删除release分支
热修复流程
- 从main创建hotfix分支
- 修复问题
- 更新patch版本号
- 创建PR到main
- 合并到main后：
- 标记发布
- 合并回develop
- 删除hotfix分支
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.
- 1mo ago First seen · 114 lines · 0 tokens per session scan A 93bc0cb53bbd
gitflow is a cursor rule published in the GitHub repository WangTingYeYe/llm-agent-study (4 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 731 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-08-31.
Other cursor rules, from other repositories
changesets
Changeset format and bump rules enforced by CI.
release-notes
Generate changelog entries and GitHub releases from git history. Categorizes commits into features, fixes, breaking changes, and docs. Supports conventional commits, PR-based grouping, and semantic versioning. Creates formatted CHANGELOG.md entries and GitHub releases.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
release-checklist
What to update with each code change or version release.
github-cli-guide
A guide on how to use the Github CLI (gh cli) especially related to creating issues via the CLI.
release-policy
Release, versioning, and signing policy for setmac.