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 cookieMonsterDev/agents-skills --skill git-docsgit clone --depth 1 https://github.com/cookieMonsterDev/agents-skillsWrote 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/cookiemonsterdev/agents-skills/git-docs)<a href="https://agentmods.dev/skills/cookiemonsterdev/agents-skills/git-docs"><img src="https://agentmods.dev/badge/skills/cookiemonsterdev/agents-skills/git-docs/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/cookiemonsterdev/agents-skills/git-docs"><img src="https://agentmods.dev/badge/skills/cookiemonsterdev/agents-skills/git-docs.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.00086 | $0.01401 |
| Opus 5.5 | $0.00034 | $0.00560 |
| Sonnet 5.5 | $0.00017 | $0.00280 |
| Haiku 4.5 | $0.00009 | $0.00140 |
Grade A, and why
git-docs 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.
How it starts
The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git questions are easy to answer from stale memory or from a hosting provider's UI docs instead of Git itself. Use this skill to ground answers in the official Git documentation and return the closest authoritative command reference or book chapter instead of guessing flag behavior.
When to Use
Use this skill when the request is about:
- Core Git commands and their exact flags:
commit,branch,checkout,switch,restore,merge,rebase,reset,log,diff,push,pull,fetch,clone,tag,stash,cherry-pick,bisect,worktree,submodule,reflog,blame,remote - Git concepts: the object model (blobs, trees, commits, refs), the index/staging area, and the working tree
- Revision syntax (
HEAD~2,main..feature,@{upstream}) and the gitrevisions reference - Branching and merging strategies, rebase workflows, and conflict resolution
- Git hooks,
.gitignore,.gitattributes, and repository configuration - Submodules and worktrees for managing multiple checkouts or nested repositories
- History rewriting: interactive rebase, filter-repo-style history surgery, and reflog recovery
- Git internals: plumbing vs porcelain commands, packfiles, and the transfer protocols
Do not use this skill for:
- GitHub-specific features (pull requests, GitHub Actions, GitHub CLI, repository settings UI). Use
github-actions-docsfor Actions, or the GitHub product docs for the rest. - GitLab-specific features (merge requests, GitLab CI/CD pipelines). Use
gitlab-ci-docsinstead. - GUI Git clients unless the question is about the underlying Git command each button runs.
Workflow
1. Classify the request
Decide which bucket the question belongs to before searching:
- Getting started and everyday workflow
- Branching, merging, and rebasing
- Undoing changes: reset, revert, restore, checkout, and reflog
- Inspecting history: log, diff, blame, and bisect
- Remote operations: fetch, pull, push, and remotes
- Advanced structures: worktrees and submodules
- Configuration, hooks, ignore/attribute files
- Internals and the object model
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 100 lines · 86 tokens per session scan A d35a80825afa
git-docs is a skill published in the GitHub repository cookieMonsterDev/agents-skills (6 stars, last pushed today), licensed MIT. It adds 86 tokens to every session and 1,401 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
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work.
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
antfu-issue-triage
Triage open issues and PRs of the current GitHub repo - find already-fixed, duplicate, and spam items, suggest labels, gauge demand from reactions and comments, then present a table of proposed actions and comments for confirmation before touching anything. Use when asked to triage, organize, clean up, or groom issues…
reproduce-and-fix-issues
Reproduce triaged Slack bugs through a configured app-control adapter, verify existing fixes, and open a bounded draft pull request only after before-and-after proof. Use only from the configured Benny repro automation.
factory-recover
Experimental workflow for finding and resuming interrupted coding runs. Use after an agent host restart or an interrupted automation.
comet-github-issue-fix
A workflow for fixing a confirmed Comet-related GitHub issue or review blocker within an isolated scope. It covers matching the work to the relevant workflow, testing the change, checking runtime results, and preparing a careful handoff.