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/gc-commit-skill)<a href="https://agentmods.dev/rules/adobedocs/ff-services-docs/gc-commit-skill"><img src="https://agentmods.dev/badge/rules/adobedocs/ff-services-docs/gc-commit-skill/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/gc-commit-skill"><img src="https://agentmods.dev/badge/rules/adobedocs/ff-services-docs/gc-commit-skill.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.00412 | $0.00412 |
| Opus 5.5 | $0.00165 | $0.00165 |
| Sonnet 5.5 | $0.00082 | $0.00082 |
| Haiku 4.5 | $0.00041 | $0.00041 |
Grade A, and why
gc-commit-skill 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
Quick commit (/gc and /gcam) — project skills
These Agent skills use User Rules → Git commit messages (imperative ~50-character subject, blank line, body bullets with 📖 for new work and ✏️ for edits).
Where they live
| Command | Skill | Purpose |
|---|---|---|
/gc |
.cursor/skills/gc/SKILL.md | Stage all (git add -A) → commit in one flow. |
/gcam |
.cursor/skills/gcam/SKILL.md | Stage all → proposed message for review → user chooses (1) commit or (2) reject (no commit on reject; staging kept unless user asks to unstage). |
When to use which
/gc— User wants stage everything and commit immediately with the standard message format./gcam— User wants to see and optionally edit the commit message first, then commit or reject.
When not to use
- Partial paths only or no staging — confirm scope; these skills default to all saved changes via
git add -A. - Message only, no staging — draft a message without running the full skill unless they ask to stage.
For message structure and examples, see gc’s SKILL.md; gcam references the same format.
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 · 29 lines · 412 tokens per session scan A 0feb293d39a2
gc-commit-skill 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 412 tokens to every session, about $0.0016 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.