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 wyattowalsh/agents --skill git-workflowgit clone --depth 1 https://github.com/wyattowalsh/agentsWrote 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/wyattowalsh/agents/git-workflow)<a href="https://agentmods.dev/skills/wyattowalsh/agents/git-workflow"><img src="https://agentmods.dev/badge/skills/wyattowalsh/agents/git-workflow/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/wyattowalsh/agents/git-workflow"><img src="https://agentmods.dev/badge/skills/wyattowalsh/agents/git-workflow.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.00044 | $0.02290 |
| Opus 5.5 | $0.00018 | $0.00916 |
| Sonnet 5.5 | $0.00009 | $0.00458 |
| Haiku 4.5 | $0.00004 | $0.00229 |
Grade A, and why
git-workflow 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.
How it starts
The opening of the file, as written. The whole thing — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Workflow
Git operations assistant. Lightweight, high-frequency tool for commit messages, PR descriptions, branch strategy, conflict resolution, code archaeology, and bisect debugging.
Scope: Git workflow operations only. NOT for code review (review), CI/CD pipelines (devops-engineer), changelogs or release notes (changelog-writer), or writing application code.
Dispatch
| $ARGUMENTS | Mode |
|---|---|
commit |
Generate conventional commit message from staged diff |
pr |
Generate PR description from branch diff |
strategy |
Recommend branch strategy for project |
conflict |
Guide merge conflict resolution |
archaeology <file or function> |
Analyze git history for code understanding |
bisect |
Assist with git bisect to find regression commits |
| Empty | Show mode menu with examples |
Canonical Vocabulary
Use these terms exactly throughout all modes:
| Term | Definition |
|---|---|
| conventional commit | Structured commit format: type(scope): subject per Conventional Commits 1.0 |
| commit type | One of: feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert |
| breaking change | Commit with ! suffix or BREAKING CHANGE: footer requiring major version bump |
| scope | Optional parenthesized component name after type: feat(auth): ... |
| trunk-based | Strategy where all developers commit to main/trunk with short-lived feature branches |
| git-flow | Strategy with develop, feature, release, and hotfix branches |
| github-flow | Simplified strategy: main + feature branches with PR-based merging |
| conflict marker | Git-inserted <<<<<<<, =======, >>>>>>> delimiters in conflicted files |
| blame | git blame annotation showing last modifier per line |
| archaeology | Using git history commands to understand why code exists |
| bisect | Binary search through commits to find the one introducing a bug |
| good/bad commit | Bisect terminology: good = before bug, bad = after bug |
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.
- data/branch-strategies.json 3.7 KB
- data/conventional-commits.json 3.6 KB
- evals/archaeology-implicit.json 524 B
- evals/bisect-assist.json 434 B
- evals/branch-strategy.json 493 B
- evals/commit-message.json 560 B
- evals/evals.json 2.4 KB
- evals/negative-control.json 363 B
- evals/pr-description.json 486 B
- references/branch-strategies.md 4.9 KB
- references/commit-and-pr-guide.md 5.1 KB
- references/history-and-debugging.md 5.1 KB
- scripts/asset_toolkit/__init__.py 303 B runs code
- scripts/asset_toolkit/_shared.py 5.6 KB runs code
- scripts/asset_toolkit/common.py 3.0 KB runs code
- scripts/asset_toolkit/package.py 43 KB runs code
- scripts/asset_toolkit/validate_evals.py 11 KB runs code
- scripts/asset_toolkit/validate_hooks.py 13 KB runs code
- scripts/asset_toolkit/validate_skill.py 3.6 KB runs code
- scripts/check.py 2.2 KB runs code
- scripts/commit-parser.py 5.8 KB runs code
- scripts/diff-summarizer.py 6.0 KB 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.
- 1mo ago First seen · 206 lines · 44 tokens per session scan A 8cf3f5d66e54
git-workflow is a skill published in the GitHub repository wyattowalsh/agents (5 stars, last pushed 1mo ago), licensed MIT. It adds 44 tokens to every session and 2,290 once invoked, about $0.0002 per session on Opus 5.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-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
enable-check-includes-strict
Enable and migrate Chromium targets and directories to checkincludesstrict = true, diagnosing and resolving header include violations as part of the checkincludesstrict LSC. Use when adding directories to the allowlist, enabling strict header checks on targets, or resolving CHECKINCLUDESSTRICTUNTRIAGED targets.
resolve-publish
Commit the validated fix and follow local-only, workflow-owned, or direct PR publication.
gsd-audit-fix
Autonomous audit-to-fix pipeline — find issues, classify, fix, test, commit.
fix-issue
Fixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to…
git-mastery
Advanced Git: rebase, bisect, reflog, cherry-pick, worktrees, LFS. Triggers: rebase, bisect, cherry-pick, reflog, force push, merge conflict, worktree.