Borrowing it
Nothing to install: this file belongs to AdobeDocs/ff-services-docs. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/AdobeDocs/ff-services-docs/main/.cursor/skills/gc/SKILL.mdgit 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/skills/adobedocs/ff-services-docs/gc)<a href="https://agentmods.dev/skills/adobedocs/ff-services-docs/gc"><img src="https://agentmods.dev/badge/skills/adobedocs/ff-services-docs/gc/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/skills/adobedocs/ff-services-docs/gc"><img src="https://agentmods.dev/badge/skills/adobedocs/ff-services-docs/gc.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.00076 | $0.00907 |
| Opus 5.5 | $0.00030 | $0.00363 |
| Sonnet 5.5 | $0.00015 | $0.00181 |
| Haiku 4.5 | $0.00008 | $0.00091 |
Grade A, and why
gc 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/gc — Stage all and commit
When to run
Apply this skill only when the user clearly wants a full-repo stage-and-commit in one step (for example /gc, “run gc”, or “stage all changes and commit”).
Do not run if the user only asked for a message draft with no commit, or if they want to stage specific paths only—confirm scope first.
For review before commit (proposed message, then user chooses commit or reject), use the gcam skill (/gcam) instead.
Steps
-
Confirm repo root — Run commands from the workspace git root (the directory that contains
.git). If unsure, rungit rev-parse --show-toplevelandcdthere. -
Stage everything — Run:
git add -AThis stages saved changes to tracked files, new files, and removals. Unsaved editor buffers are not in git until the user saves.
-
Inspect what will be committed — Use
git statusand, if needed,git diff --cached --stat(or full--cached) so the message matches the actual change set. -
Write the commit message using the User Rules → Git commit messages format (see below). Base the subject and bullets on the staged diff, not on assumptions.
-
Commit — Prefer a single commit with a multi-line message. For example, write the message to a file and commit:
git commit -F /path/to/commit-msg.txtOr use multiple
-marguments: first-mfor the subject line, second-mfor the body (paragraph with bullet lines). -
Report — Show the user the short hash, subject line, and a one-line summary of what was committed.
Commit message format (required)
Follow the user’s Git commit rules exactly:
Subject line (first line only)
- About 50 characters or fewer
- Imperative mood (e.g. “Add…”, “Fix…”, “Update…”)
- No trailing period on the subject line
Blank line
- One blank line after the subject before the body
Body (detailed description)
- Wrap body lines at about 72 characters where practical
- Use bullet lines; each bullet must start with exactly one of:
- 📖 — net-new content: new files, new sections, new features, new headers, greenfield lines
- ✏️ — modifications: edits to existing lines, updates to sections, refactors, changes to current content
- Apply 📖 or ✏️ to every body bullet so additions vs edits are explicit
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 · 102 lines · 76 tokens per session scan A ba50712c2970
gc is a skill published in the GitHub repository AdobeDocs/ff-services-docs (4 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 76 tokens to every session and 907 once invoked, about $0.0003 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 skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…