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 agentmods add skills/pledgeandgrow/pledge-skills/gitnpx skills add pledgeandgrow/pledge-skills --skill gitgit clone --depth 1 https://github.com/pledgeandgrow/pledge-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/pledgeandgrow/pledge-skills/git)<a href="https://agentmods.dev/skills/pledgeandgrow/pledge-skills/git"><img src="https://agentmods.dev/badge/skills/pledgeandgrow/pledge-skills/git.svg" alt="Measured on agentmods" 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 | $0.00032 | $0.01843 |
| Opus 5 | $0.00016 | $0.00922 |
| Sonnet 5 | $0.00006 | $0.00369 |
| Haiku 4.5 | $0.00003 | $0.00184 |
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 5d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git
Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency.
Version: Git 2.49
Documentation: git-scm.com/docs
Book: Pro Git
Quick Reference
| Topic | File |
|---|---|
| Introduction (what is Git, VCS types, installing, first-time setup) | introduction.md |
| Repositories (init, clone, recording changes, history, undoing, remotes, tagging, aliases) | repositories.md |
| Branching and Merging (branch, switch, merge, conflicts, stash, tag, worktree, rebase, workflows) | branching-and-merging.md |
| Sharing and Updating (fetch, pull, push, remote, submodule, refspecs) | sharing-and-updating.md |
| Inspection and Comparison (show, log, diff, difftool, range-diff, shortlog, describe, revision selection) | inspection-and-comparison.md |
| Patching (apply, cherry-pick, rebase, revert, format-patch, patch workflows) | patching.md |
| Debugging (bisect, blame, grep, finding bugs) | debugging.md |
| Administration (clean, gc, fsck, reflog, filter-branch, instaweb, archive, bundle, maintenance) | administration.md |
| Server Admin (protocols, SSH setup, git daemon, Smart HTTP, GitWeb, hosting, security) | server-admin.md |
| Email (format-patch, am, send-email, imap-send, request-pull, patch workflows) | email.md |
| External Systems (svn, fast-import, p4, migrating to Git) | external-systems.md |
| Configuration (git config, levels, settings, aliases, credentials, signing, includeIf, performance) | configuration.md |
| Git Tools (revision selection, interactive staging, stashing, cleaning, signing, searching, rewriting history, reset, advanced merging, rerere, submodules, bundling, replace, credentials) | git-tools.md |
| Git Internals (plumbing, objects, refs, packfiles, refspec, transfer protocols, plumbing commands, environment variables) | git-internals.md |
| Guides (gitignore, gitattributes, hooks, gitmodules, workflows) | guides.md |
| Distributed Git (workflows, contributing, maintaining, commit guidelines) | distributed-git.md |
| GitHub (account setup, SSH, contributing, maintaining, organizations, GitHub CLI, Actions, API) | github.md |
| Embedding Git (libgit2, JGit, go-git, pygit2, rugged, nodegit, LibGit2Sharp, scripting) | embedding-git.md |
| Sparse Checkout, Scalar, Partial Clone (sparse-checkout, backfill, maintenance, pack-refs, prune, diagnose, fast-export) | sparse-checkout.md |
| File Formats and Protocols (repository layout, index, pack, bundle, commit-graph, chunk, signature, wire protocols v0/v1/v2, namespaces, remote-helpers, mailmap, diffcore) | file-formats-and-protocols.md |
| Additional Commands (annotate, merge-tree, show-branch, whatchanged, cherry, ls-remote, name-rev, commit-graph, pack-objects, interpret-trailers, stripspace, credential, GUI tools, CVS commands) | additional-commands.md |
| Tutorials and Migration (gittutorial, gittutorial-2, gitcore-tutorial, CVS migration, CVS-to-Git command mapping, diffcore) | tutorials-and-migration.md |
What ships with it
22 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.
- additional-commands.md 13 KB
- administration.md 7.0 KB
- branching-and-merging.md 8.6 KB
- configuration.md 7.8 KB
- debugging.md 5.4 KB
- distributed-git.md 5.9 KB
- email.md 5.7 KB
- embedding-git.md 6.6 KB
- external-systems.md 4.3 KB
- file-formats-and-protocols.md 11 KB
- git-internals.md 9.8 KB
- git-tools.md 8.2 KB
- github.md 6.9 KB
- guides.md 8.8 KB
- inspection-and-comparison.md 6.3 KB
- introduction.md 4.7 KB
- patching.md 6.1 KB
- repositories.md 9.7 KB
- server-admin.md 6.2 KB
- sharing-and-updating.md 7.3 KB
- sparse-checkout.md 7.0 KB
- tutorials-and-migration.md 9.7 KB
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.
- 5d ago First seen · 106 lines · 32 tokens per session scan A d1820e25f63a
git-docs is a skill published in the GitHub repository pledgeandgrow/pledge-skills (10 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 1,843 once invoked, about $0.0002 per session on Opus 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
git-workflows
Git version control, branching strategies, and collaboration patterns.
git-essentials
Expert Git workflow assistance for branching, merging, rebasing, conflict resolution, and history management. Use when working with Git operations beyond simple commits.
github-ops
GitHub repository operations — issues, PRs, code search, and config-as-code workflows. Use when creating a GitHub issue for a network finding, opening a pull request for a config change, searching repos for IP or VLAN references, or committing an audit report to a repository.
agenthub
Browse, create, and complete tasks on Clawsy AgentHub — a distributed task platform for AI agents. Create tasks from GitHub repos, PDF/DOCX/PPTX/audio URLs, or plain text. Use custom LLM validation, earn karma. Categories: content, data, research, creative.
git-workflows
Git workflows, branching strategies (gitflow, trunk-based), Conventional Commits, commit message quality, version control best practices, and pull-request conventions — with deterministic convention checker script. Use proactively when reviewing commit message quality before merge, enforcing branch naming conventions…
git-workflow-and-versioning
Git workflow and version control best practices. Use when committing code, creating branches, preparing pull requests, or managing release versioning. Use when structuring commit messages or planning a branching strategy.