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/gcam/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/gcam)<a href="https://agentmods.dev/skills/adobedocs/ff-services-docs/gcam"><img src="https://agentmods.dev/badge/skills/adobedocs/ff-services-docs/gcam/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/gcam"><img src="https://agentmods.dev/badge/skills/adobedocs/ff-services-docs/gcam.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.00081 | $0.00947 |
| Opus 5.5 | $0.00032 | $0.00379 |
| Sonnet 5.5 | $0.00016 | $0.00189 |
| Haiku 4.5 | $0.00008 | $0.00095 |
Grade A, and why
gcam 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/gcam — Stage all, propose message, review, then commit or reject
When to run
Apply when the user wants staging plus a proposed commit message but no commit until they approve—for example /gcam, “gcam”, “stage all and let me edit the commit message”, or “propose a commit then I’ll choose commit or reject”.
Do not run when the user wants an immediate commit with no review—use the gc skill (/gc) instead.
Steps (first message)
-
Repo root — Run from the git root (
git rev-parse --show-toplevelif needed). -
Stage everything — Run:
git add -A -
Inspect the staged set — Use
git statusandgit diff --cached/--statso the draft message matches what is staged. -
Draft the commit message using User Rules → Git commit messages (same rules as
gc: imperative ~50-character subject, blank line, body bullets with 📖 / ✏️, ~72-character wrap). See .cursor/skills/gc/SKILL.md for the full template and examples. -
Present for review — Output the message in a single fenced code block labeled clearly so the user can copy and edit it, for example:
- Proposed commit message (copy/edit below)
-
Pause for user decision — Do not run
git commityet. End with a short prompt like:- Review the proposed message above. You may reply with an edited full message in a code block if you want changes.
- Then choose:
1orcommit— Commit using the final message (your edited version if you sent one; otherwise the proposal).2orreject— Do not commit. Staged files stay staged unless you ask to unstage.
-
If nothing is staged after
git add -A, say so and stop (same asgc).
Steps (user’s follow-up message)
Interpret the reply:
| User intent | Action |
|---|---|
1, commit, or equivalent and (optional) a full commit message in a code block |
Commit with that message. If they chose 1 but no new message, use the last proposed message from the previous turn. |
2, reject, or equivalent |
Do not run git commit. Confirm that the commit was skipped. Staged changes remain staged by default. |
| Edited message only (code block) without 1 or 2 | Ask them to reply with 1 (commit with that text) or 2 (reject). |
| Ask to unstage after reject | Run git reset HEAD (or git restore --staged . if appropriate for their Git version/workflow) from repo root and confirm. |
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 · 66 lines · 81 tokens per session scan A 987940bbfe25
gcam is a skill published in the GitHub repository AdobeDocs/ff-services-docs (4 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 81 tokens to every session and 947 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…