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 vanja-emichi/a0_agent_skills --skill git-workflow-and-versioninggit clone --depth 1 https://github.com/vanja-emichi/a0_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/vanja-emichi/a0_agent_skills/git-workflow-and-versioning)<a href="https://agentmods.dev/skills/vanja-emichi/a0_agent_skills/git-workflow-and-versioning"><img src="https://agentmods.dev/badge/skills/vanja-emichi/a0_agent_skills/git-workflow-and-versioning/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/vanja-emichi/a0_agent_skills/git-workflow-and-versioning"><img src="https://agentmods.dev/badge/skills/vanja-emichi/a0_agent_skills/git-workflow-and-versioning.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.00045 | $0.02436 |
| Opus 5 | $0.00023 | $0.01218 |
| Sonnet 5 | $0.00009 | $0.00487 |
| Haiku 4.5 | $0.00005 | $0.00244 |
Grade A, and why
git-workflow-and-versioning 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 9d 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 — 377 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Workflow and Versioning
Overview
Git history is documentation. A well-structured commit history lets you understand what changed, why it changed, and who changed it — weeks or months later. This skill covers commit practices, branching strategies, pull request quality, and semantic versioning.
When to Use
- Writing commit messages
- Creating feature branches
- Preparing pull requests for review
- Planning a release or version bump
- Reviewing git history to understand context
Commit Messages
The Conventional Commits Format
<type>(<scope>): <short description>
[optional body]
[optional footer(s)]
Types:
| Type | When to Use |
|---|---|
feat |
New feature or capability |
fix |
Bug fix |
docs |
Documentation changes only |
style |
Formatting, whitespace (no logic change) |
refactor |
Code restructuring (no feature, no bug fix) |
test |
Adding or fixing tests |
chore |
Build process, dependencies, tooling |
perf |
Performance improvement |
ci |
CI/CD configuration changes |
Examples:
# Good: clear type, scope, and description
git commit -m "feat(tasks): add priority levels to task creation"
git commit -m "fix(auth): handle expired tokens gracefully"
git commit -m "refactor(api): extract validation middleware"
git commit -m "docs(readme): add deployment instructions"
# With body for non-obvious changes
git commit -m "fix(tasks): prevent duplicate task creation on fast double-click
Added debounce to the create button click handler and optimistic
update deduplication in the React Query mutation. The underlying
API already had idempotency guards, but the UI was sending multiple
requests before the first one resolved.
Fixes #234"
# Breaking changes
git commit -m "feat(api)!: change task status enum values
BREAKING CHANGE: Status values changed from 'todo/done' to
'pending/completed' to match the new backend schema.
Migrate existing data with: npm run migrate:status"
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.
- 9d ago First seen · 377 lines · 45 tokens per session scan A 5751dca5a888
git-workflow-and-versioning is a skill published in the GitHub repository vanja-emichi/a0_agent_skills (5 stars, last pushed 1mo ago), licensed MIT. It adds 45 tokens to every session and 2,436 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-workflow
Use when naming or scoping a branch, writing or fixing a commit message, picking the gitmoji for a commit, untangling history (rebase versus merge versus squash), or cutting a versioned release — the portable git-convention layer for any repo. Covers gitmoji + Conventional Commits, SemVer tags, branch hygiene…
git-workflow
Git branching, commit conventions, rebase vs merge, conflict resolution, and release tagging. Use when setting up a git workflow, writing commits, resolving conflicts, or preparing a release.
git-workflow-automation
Expert Git workflow automation for commit message generation, branch naming, PR description writing, changelog generation, merge conflict resolution, and release management. Activates when users say "write a commit message", "create a PR", "generate changelog", "branch name for", "resolve merge conflict", "cut a…
git-workflow
Covers the full git workflow for a software project: branch naming conventions, commit message authoring (Conventional Commits standard), PR description templates, and merge strategy advice. It produces ready-to-use git artefacts, not generic advice.
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
comet-safe-delivery
A Chinese-language procedure for safely delivering specified Comet changes through Git. It covers checking worktrees and unrelated edits, staging exact files, validating hooks, and authorized commits or pushes.