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.
npx skills add samzong/gmc --skill gmcgit clone --depth 1 https://github.com/samzong/gmcWrote 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/samzong/gmc/gmc)<a href="https://agentmods.dev/skills/samzong/gmc/gmc"><img src="https://agentmods.dev/badge/skills/samzong/gmc/gmc/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/samzong/gmc/gmc"><img src="https://agentmods.dev/badge/skills/samzong/gmc/gmc.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.00123 | $0.01518 |
| Opus 5.5 | $0.00049 | $0.00607 |
| Sonnet 5.5 | $0.00025 | $0.00304 |
| Haiku 4.5 | $0.00012 | $0.00152 |
Grade A, and why
gmc 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 7d 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IRON LAW: ALL WORKTREE OPERATIONS MUST USE gmc wt <subcommand>. NEVER INVENT gmc add, gmc rm, gmc prune, gmc clone, OR OTHER TOP-LEVEL WORKTREE COMMANDS.
gmc
Use $ARGUMENTS and the user's words to route into exactly one mode.
Copy this checklist and check off items as you complete them:
- Step 0: Parse intent [BLOCKING]
- Classify the request as
commit,wt add,wt prune,wt share,wt sync,wt rm,wt ls,wt dup,wt pr-review, ortag - If the intent is unclear, ask one focused question before running commands
- Classify the request as
- Step 1: Validate context [BLOCKING]
- Confirm
gmcexists - Confirm the current directory is a git repo when the command needs repo context
- If the action depends on GitHub state, confirm
ghworks first
- Confirm
- Step 2: Preview plan [REQUIRED]
- Show the exact command you plan to run
- For destructive or bulk actions, prefer
--dry-runfirst
- Step 3: Execute exactly one workflow
-
commit -
wt add -
wt prune -
wt share - other
gmc wtsubcommand ortag
-
- Step 4: Report result
- State the exact command run
- Report the created path, cleaned worktrees, synced resources, or generated message
- State what was not run
Routing
commituses top-levelgmc- Any worktree action uses
gmc wt <subcommand> - If the user says
gmc add, translate it togmc wt addand say so - If the user wants generic git help without
gmc, do not use this skill
Common commands
gmcgmc -ygmc -a -ygmc -a -y -p "context"gmc --dry-rungmc wt add <name>gmc wt add <name> --syncgmc wt add <name> -b <branch>gmc wt lsgmc wt list -Agmc wt rm <name>gmc wt rm -D <name>gmc wt prunegmc wt syncgmc wt share lsgmc wt share add <path> --strategy copygmc wt share add <path> --strategy linkgmc wt share syncgmc tag
Workflow: commit mode
- Use top-level
gmc, notgmc wt - Default to interactive
gmcunless the user explicitly wants automation - Ask before
gmc -a -ybecause it stages all files and auto-confirms - Use
gmc --dry-runwhen the user wants a suggested message without committing
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.
- 7d ago Changed · +1 lines 29b929e24788
- 8d ago Changed · +5 lines 849f5c55daf7
- 17d ago Changed · +2 lines e23846a416fd
- 1mo ago Changed · +1 lines c74a7e73b313
- 1mo ago First seen · 115 lines · 123 tokens per session scan A 8438f608f98b
gmc is a skill published in the GitHub repository samzong/gmc (28 stars, last pushed 7d ago), licensed MIT. It adds 123 tokens to every session and 1,518 once invoked, about $0.0005 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-30.
Other skills, from other repositories
caveman-commit
Write a Conventional Commits message compressed to intent only. Use for "write a commit", "commit message", /commit or /caveman-commit.
contextual-commit
Write contextual commits that capture intent, decisions, and constraints alongside code changes. Use when committing code, finishing a task, or when the user asks to commit. Extends Conventional Commits with structured action lines in the commit body that preserve WHY code was written, not just WHAT changed.
resolve-publish
Commit the validated fix and follow local-only, workflow-owned, or direct PR publication.
feature-publish
Commit the feature, write the PR body, publish in the selected mode, and drive the PR.
meta-pre-commit-quality-gate
Run three quality gates (ruff + mypy + pytest) in parallel over the staged diff, then arbitrate a single BLOCK/APPROVE verdict. Use before committing changes locally when you want a comprehensive pre-commit gate beyond per-file linting — exactly the same gate set CI enforces.
commit-push-pr
Commit current changes, push to remote, and create or update a pull request. Use when the user wants to commit and create a PR, push changes and open a pull request, or ship their current work as a PR.