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 shennawardana23/skillme --skill git-workflow-and-versioninggit clone --depth 1 https://github.com/shennawardana23/skillmeWrote 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/shennawardana23/skillme/git-workflow-and-versioning)<a href="https://agentmods.dev/skills/shennawardana23/skillme/git-workflow-and-versioning"><img src="https://agentmods.dev/badge/skills/shennawardana23/skillme/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/shennawardana23/skillme/git-workflow-and-versioning"><img src="https://agentmods.dev/badge/skills/shennawardana23/skillme/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.00068 | $0.02086 |
| Opus 5 | $0.00034 | $0.01043 |
| Sonnet 5 | $0.00014 | $0.00417 |
| Haiku 4.5 | $0.00007 | $0.00209 |
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 6d 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 — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Workflow and Versioning
Commits are save points, branches are sandboxes, and history is documentation. A version number is the separate promise you make to consumers of your code — the moment anything outside your own working copy depends on a piece of code, "latest on main" stops being a sufficient answer to "what am I running, and is it safe to upgrade?"
Trunk-based development (default)
Keep main always deployable. Work in feature branches that merge back
within 1–3 days — long-lived branches accumulate merge risk every day
they exist, and DORA/Accelerate research consistently correlates
trunk-based development with high-performing engineering teams. Prefer
a feature flag over a long-lived branch for anything incomplete (see
ci-cd-and-automation).
main ──●──●──●──●──●──●──●── (always deployable)
╲ ╱ ╲ ╱
●──●─╱ ●──╱ ← short-lived feature branches (1-3 days)
Commit discipline
Commit each working increment, not one giant commit at the end — each commit is a point you can revert to if the next change breaks something. Each commit does one logical thing; don't mix a refactor with a feature, or formatting with behavior change, in the same commit.
# Good: atomic, self-contained commits
a1b2c3d feat: add reservation cancellation endpoint
d4e5f6g refactor: extract status-transition validation to its own function
h7i8j9k test: add table-driven tests for cancellation edge cases
# Bad: everything mixed together
x1y2z3a add cancellation, fix unrelated bug, reformat whole file, bump deps
Messages explain why, not just what:
feat: add email validation to registration endpoint
Prevents malformed addresses from reaching the database. Uses the
same validation approach as auth.ts for consistency.
Types: feat, fix, refactor, test, docs, chore. Target ~100–300
lines per commit/PR; split anything approaching 1000 lines.
Branching
feature/<short-description> feature/reservation-cancellation
fix/<short-description> fix/duplicate-charge-on-retry
chore/<short-description> chore/bump-go-version
refactor/<short-description> refactor/reservation-service
What ships with it
1 file 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.
- 6d ago First seen · 214 lines · 68 tokens per session scan A c7d66c1c30fc
git-workflow-and-versioning is a skill published in the GitHub repository shennawardana23/skillme (2 stars, last pushed 12d ago), licensed Apache-2.0. It adds 68 tokens to every session and 2,086 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple…
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.
implement-suggestion
Implements review-comment suggestions across one or more PRs. Multi-PR mode (default when $ARGUMENTS contains PR URLs; empty $ARGUMENTS auto-detects the active PR) per PR: resolves a worktree, fetches every actionable comment from both human teammates AND AI code-review bots (claude[bot], coderabbitai[bot], …)…
pr-review
One-shot read-only review of a GitHub PR — dispatches the pr-reviewer agent and reports its verdict and findings without touching your code. The short entry point for "review this PR" when you do not want an apply-and-converge loop. Also writes maintainer relevance rules via /pr-review remember . Invoke with…
conventional-commits
Enforce, validate, lint, and manage Conventional Commits across git repositories. Generates semantic changelogs and installs git hooks. Use this skill whenever the user mentions commit messages, commit conventions, conventional commits, semantic versioning, changelogs, commit linting, git hooks for commits, or wants…
changelog
Use when writing a changelog or release notes. Covers what belongs in one, writing for users rather than for git, semantic versioning, and documenting breaking changes so nobody is surprised.