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/AdobeDocs/ff-services-docsWrote 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/adobedocs/ff-services-docs/commit-rules)<a href="https://agentmods.dev/rules/adobedocs/ff-services-docs/commit-rules"><img src="https://agentmods.dev/badge/rules/adobedocs/ff-services-docs/commit-rules/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/adobedocs/ff-services-docs/commit-rules"><img src="https://agentmods.dev/badge/rules/adobedocs/ff-services-docs/commit-rules.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.00726 | $0.00726 |
| Opus 5.5 | $0.00290 | $0.00290 |
| Sonnet 5.5 | $0.00145 | $0.00145 |
| Haiku 4.5 | $0.00073 | $0.00073 |
Grade A, and why
commit-rules 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.
How it starts
The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git commit messages
Always apply this rule. When you draft or generate a git commit message (for example in the Source Control commit box or when asked in Agent chat), follow this format.
Subject line (first line only)
- Around 50 characters or fewer.
- Summarize the change in imperative mood (e.g. “Add…”, “Fix…”, “Refactor…”).
Blank line
Leave one blank line after the subject before the body.
Body (detailed description)
- Wrap lines at about 72 characters (including the bullet prefix and space).
- Use bullet lines for the explanation. Each bullet must start with exactly one of these markers:
📖 (adds)
Use when the change adds something new: new files, new sections, new features, new headers, net-new lines, or other greenfield content.
✏️ (modifies)
Use when the change modifies existing work: edits to existing lines, updates to existing sections, refactors of existing code, or changes to current content.
🆕 (TOC / feature registration)
Use the single character 🆕 when the change adds an entry to a repository table of contents or navigation config file (for example TOC.md, config.md, or similar) that registers a new feature, topic, or page. This usually means a new item appears in the doc or site nav because of that edit.
🗑️ (removes)
Use the single character 🗑️ when entire content is removed from a page or file—not a light edit, but a full deletion. Typical cases:
- A section removed (content under a heading marked with
#through######) - An image removed (for example
or asset reference dropped entirely) - A code block removed (fenced or indented block gone completely)
- A component or include removed (for example Experience League shortcodes, includes, or custom MDX-style blocks)
Do not use 🗑️ for small wording tweaks inside a section; use ✏️ for those. Use 🗑️ when the heading (and everything under it), the image, the block, or the component no longer appears at all.
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 · 73 lines · 726 tokens per session scan A ed6846361fe5
commit-rules is a cursor rule published in the GitHub repository AdobeDocs/ff-services-docs (4 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 726 tokens to every session, about $0.0029 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
git
Git workflow — commit format, push policy, and PR process.
commit-sponsors
Every git commit message must acknowledge BetterDesk supporters.
no-ai-contributors
Never add AI tools as git authors or project contributors.
git-discipline
Commit, push, and branching rules. Owns ALL git behavior; other files state only their deviations.
git-commit-standards
Enforce structured Git commit messages.
conventional-commits
Use the Conventional Commit Messages specification to generate commit messages.