When your branch is ready for review, a focused Git skill can handle the next commit and pull request. Choose one that fits your work and keeps its session cost visible.
What a Git skill puts in the session
A skill is a folder of instructions the model opens when it decides it needs them. A branch is a separate line of work. A pull request is a proposed code change that others review before merging.
Of 12,055 skills, 11,727 load their name and description every session. The rest wait until you ask for them. When invoked, the full body enters the context. The context is everything the model can see while it answers you.
The original is the first copy of a file we saw; everything matching it afterwards is a copy. Of these Git skills, 11,239 are originals and none is a near duplicate. This separates source files from repeated versions.
What Git skills cost each session
A token is the unit your AI plan bills by, about three quarters of a word. The median Git skill uses 51 tokens every session. That is closer to a sticky note than a manual.
The 90th percentile is 120 tokens. At 20 sessions a day, the 51-token median becomes 1,020 tokens of repeated context.
An on-demand skill has a 1,030-token median full body once you use it. The maximum every-session load is 569 tokens, from git-rebase-stalls-async-post-commit-hook.
What the safety scan found in Git skills
The scan graded 11,371 skills A, 269 B, 415 C or D, and 0 E or F. An A means the scan found nothing it treats as risky. It does not mean the file has no capability worth understanding.
The scan flagged 552 of them for network calls, 260 for a recursive force delete and 166 for reading agent configuration directories. The fix-ci-failures skill has a network finding. The publish-extension skill includes remote-code execution concerns. The turborepo-caching skill has a recursive force-delete finding.
Each finding gives you a line to inspect. It does not decide whether the skill belongs in your project.
Six Git skills for commits, branches and pull requests
Each entry shows what the skill does, its lines, its session load, and its copy status.
- fix-ci-failures: investigates failed pull-request checks, reads logs, and helps fix the cause. 60 tokens every session, 270 lines, original, 0 copies.
- gh-stack: manages dependent branches and stacked pull requests with gh-stack. 80 tokens every session, 184 lines, original, 5 copies.
- dsh-pre-push-checks: chooses the smallest useful checks before pushing a branch or requesting review. 68 tokens every session, 128 lines, original, 6 copies.
- pr-creator: prepares pull requests using the repository’s templates and rules. 31 tokens every session, 94 lines, original, 2 copies.
- prepare-providers-documentation: sorts pending pull requests and writes the release notes for Airflow providers, a pull-request job tied to that repository. 113 tokens every session, 1,152 lines, original, 0 copies.
- draft-release-notes: turns merged pull requests into categorised Prisma release notes. 174 tokens every session, 305 lines, original, 1 copy.
When a Git hook beats a skill
A hook is a shell command your agent runs for you when something happens. Choose one when a check must run at a fixed event, such as before a push. A skill waits for the model to decide it is relevant.
Use a Git skill when you need judgement about commits, branches or pull requests. Use a hook when the same command must run every time and should not depend on the model remembering it.
Questions people ask
Will these Git skills work in Cursor or Claude Code? The breakdown lists 11,268 skills for Claude Code and 139 for Cursor. Check the install option for your agent before adding one.
How much context can one skill use? The median body across these Git skills, once one is open, is 1,238 tokens. Prefer a smaller guide when several skills and project files already compete for your context.
Should an A grade settle the decision? No. Install it only when its purpose and any network access make sense for your repository.
Do it now
Run npx agentmods add <slug> to install one mod by its catalogue slug, then browse all Git skills.