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 JPeetz/agent-skills --skill git-workflow-automationgit clone --depth 1 https://github.com/JPeetz/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/jpeetz/agent-skills/git-workflow-automation)<a href="https://agentmods.dev/skills/jpeetz/agent-skills/git-workflow-automation"><img src="https://agentmods.dev/badge/skills/jpeetz/agent-skills/git-workflow-automation.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.1 | $0.00103 | $0.02192 |
| Opus 5 | $0.00051 | $0.01096 |
| Sonnet 5 | $0.00021 | $0.00438 |
| Haiku 4.5 | $0.00010 | $0.00219 |
Grade A, and why
git-workflow-automation 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
What ships with it
9 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.
- CHANGELOG.md 1.7 KB
- evals/evals.json 2.4 KB
- LICENSE 12 B
- references/conventional-commits-spec.md 1.5 KB
- references/keep-a-changelog-format.md 2.0 KB
- references/semver-cheatsheet.md 1.4 KB
- scripts/generate-changelog.sh 1.2 KB runs code
- scripts/next-version.sh 1.1 KB runs code
- scripts/validate-commits.sh 1002 B runs code
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 · 269 lines · 103 tokens per session scan A d6df9a0e0e7a
git-workflow-automation is a skill published in the GitHub repository JPeetz/agent-skills (5 stars, last pushed 6d ago), with no licence file. It adds 103 tokens to every session and 2,192 once invoked, about $0.0005 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…
conventional-commits
Write well-structured conventional commit messages. Use when committing code changes to ensure consistent, parseable commit history that enables automated changelogs and semantic versioning.
changelog-generator
Generate beautiful CHANGELOG.md from git commits following Keep a Changelog format.
commit-pr
Mandatory Codex/Copilot publication adapter for opencode-swarm. Use for every GitHub issue assignment that results in code changes, commits, pushes, draft PRs, PR body edits, PR readying, release notes, or CI closeout. Must be loaded before git push, gh pr create, gh pr edit, or gh pr ready. Routes to the single…
git-workflow
Guides you through Git workflows — branching strategies, commit conventions, merge conflict resolution, and release management. Use when working with Git repositories or when the user asks about version control best practices.
changelog-automation
Git history'den otomatik changelog, semantic versioning, release notes, conventional commits.