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 h4vzz/awesome-ai-agent-skills --skill version-controlgit clone --depth 1 https://github.com/h4vzz/awesome-ai-agent-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/h4vzz/awesome-ai-agent-skills/version-control)<a href="https://agentmods.dev/skills/h4vzz/awesome-ai-agent-skills/version-control"><img src="https://agentmods.dev/badge/skills/h4vzz/awesome-ai-agent-skills/version-control/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/h4vzz/awesome-ai-agent-skills/version-control"><img src="https://agentmods.dev/badge/skills/h4vzz/awesome-ai-agent-skills/version-control.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.00030 | $0.01790 |
| Opus 5.5 | $0.00012 | $0.00716 |
| Sonnet 5.5 | $0.00006 | $0.00358 |
| Haiku 4.5 | $0.00003 | $0.00179 |
Grade A, and why
version-control 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.
This is a copy
94% identical to version-control — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Version Control with Git
This skill equips an AI agent to perform the full spectrum of Git-based version control tasks, from initializing a repository and crafting atomic commits to orchestrating branching strategies, resolving merge conflicts, and configuring automation with hooks. It covers both everyday workflows and advanced operations needed for professional team collaboration.
Workflow
-
Assess Repository State: Run
git status,git log --oneline -10, andgit branch -ato understand the current branch, uncommitted changes, recent history, and available remotes. This context determines which operations are safe to perform. -
Stage and Commit Changes: Group related changes into atomic commits. Write commit messages that start with a concise summary line (50 characters or fewer), followed by a blank line and an explanatory body when the change is non-trivial. Follow the project's commit convention (Conventional Commits, Angular style, etc.) if one exists.
-
Branch Management: Create feature, bugfix, or release branches from the appropriate base. Use a consistent naming convention such as
feat/short-description,fix/issue-123, orrelease/1.2.0. Delete stale branches after merging to keep the branch list clean. -
Synchronize with Remote: Fetch and pull regularly to stay up to date. Push feature branches with the
-uflag on first push. Before merging, rebase or merge the base branch into the feature branch to resolve conflicts early in an isolated context. -
Resolve Conflicts: When conflicts arise, inspect the conflicting files, understand both sides of the change, choose the correct resolution (or combine both), mark the file as resolved with
git add, and complete the merge or rebase. Always run tests after resolution to confirm correctness. -
Automate with Hooks and CI: Set up Git hooks (pre-commit for linting/formatting, commit-msg for message validation, pre-push for test runs) and ensure
.gitignorecovers build artifacts, environment files, and OS metadata. Integrate with CI pipelines to enforce quality gates on every push.
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 · 143 lines · 30 tokens per session scan A 166013b225f6
version-control is a skill published in the GitHub repository h4vzz/awesome-ai-agent-skills (36 stars, last pushed 22d ago), licensed MIT. It adds 30 tokens to every session and 1,790 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 94% identical to version-control, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
Git CLI
Help with safe Git workflows (branching, rebasing, release tags) and troubleshooting.
git-workflow
Git workflow patterns including branching strategies, commit conventions, merge vs rebase, conflict resolution, and collaborative development best practices for teams of all sizes.
run-work
Execute a work unit end-to-end: sequence tasks by dependency, implement, test between tasks, commit, and track progress. Use to deliver a complete feature in one session. Invoked as /agiflow:run-work . Uses getworkunit, listtasks, updatetask, getworkunitprogress.
writing-modpack-changelog
Use when cutting a modpack release. Creates /docs/release-changelog.md if absent; appends a new version section with grouped changes. Triggers - 'cut a release', 'release notes', 'changelog', 'v1.2.3 changes', 'what changed since last version'.
claude-devfleet
Orchestrate multi-agent coding tasks via Claude DevFleet — plan projects, dispatch parallel agents in isolated worktrees, monitor progress, and read structured reports.
git-worktree-isolation
A Git workflow that gives each development task its own worktree, which is a separate working directory linked to a branch. It keeps parallel tasks and experiments apart from the main checkout.