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/flyeric0212/cursor-history-linksWrote 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/flyeric0212/cursor-history-links/git)<a href="https://agentmods.dev/rules/flyeric0212/cursor-history-links/git"><img src="https://agentmods.dev/badge/rules/flyeric0212/cursor-history-links/git/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/flyeric0212/cursor-history-links/git"><img src="https://agentmods.dev/badge/rules/flyeric0212/cursor-history-links/git.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.00006 | $0.00311 |
| Opus 5.5 | $0.00002 | $0.00124 |
| Sonnet 5.5 | $0.00001 | $0.00062 |
| Haiku 4.5 | $0.00001 | $0.00031 |
Grade A, and why
git 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- git — 91% identical, 2 lines differ
What it actually says
Git 规范
提交规范
git 提交记录样例：[type]: [description]。一个具体的例子, docs: 更新 README 文件。 以下是 type 的枚举值：
- feat: 新增功能
- fix: 修复 bug
- docs: 文档注释
- style: 代码格式(不影响代码运行的变动)
- refactor: 重构、优化(既不增加新功能, 也不是修复bug)
- perf: 性能优化
- test: 增加测试
- chore: 构建过程或辅助工具的变动
- revert: 回退
- build: 打包
分支管理
- main/master: 主分支，保持稳定可发布状态
- develop: 开发分支，包含最新开发特性
- feature/*: 功能分支，用于开发新功能
- bugfix/*: 修复分支，用于修复bug
- release/*: 发布分支，用于准备发布
重要原则
- 重要：不要自动提交 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.
- 1mo ago First seen · 33 lines · 6 tokens per session scan A 5b8c96147168
git is a cursor rule published in the GitHub repository flyeric0212/cursor-history-links (261 stars, last pushed 2d ago), licensed MIT. It adds 6 tokens to every session and 311 once invoked, about $0.0000 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-09-01.
Other cursor rules, from other repositories
conventional-commits
This rule defines the format for creating commit messages.
git-conventional-commit-messages
Cursor rules for Git development with conventional commit messages integration.
python-github-setup-cursorrules-prompt-file
Cursor rules for Python development with GitHub setup integration.
commit-message-generation-rule
Rules for writing consistent Git commit messages, using labels such as feat for a feature, fix for a bug, and docs for documentation. A commit message records one set of code changes.
commit-authorship
Git commits must be authored by the user only (no Cursor co-author).
pr-template-cursorrules-prompt-file
Cursor rules for PR development with template integration.