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 agentmods add commands/jezweb/claude-skills/git-workflowgit clone --depth 1 https://github.com/jezweb/claude-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/commands/jezweb/claude-skills/git-workflow)<a href="https://agentmods.dev/commands/jezweb/claude-skills/git-workflow"><img src="https://agentmods.dev/badge/commands/jezweb/claude-skills/git-workflow.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 | $0.00013 | $0.00099 |
| Opus 5 | $0.00006 | $0.00049 |
| Sonnet 5 | $0.00003 | $0.00020 |
| Haiku 4.5 | $0.00001 | $0.00010 |
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 3d 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.
What it actually says
Load the git-workflow skill.
Parse $ARGUMENTS for action:
pr— prepare a pull requestclean— clean up merged/stale branchesconflicts— resolve merge conflictstag— create a version tag
Default: detect what's needed from git 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.
- 3d ago First seen · 15 lines · 13 tokens per session scan A af215b9bdabd
git-workflow is a command published in the GitHub repository jezweb/claude-skills (993 stars, last pushed 2mo ago), licensed MIT. It adds 13 tokens to every session and 99 once invoked, about $0.0001 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-30.
Other commands, from other repositories
README
Git workflow and quality assurance commands for the claude-skills repository.
minutes-ideas
Surface recent voice memos and ideas captured from any device. Use when the user asks "what ideas did I have?", "what were my recent memos?", "what did I record while walking?", or wants to recall a captured thought.
engage.actions
Execute Phase 7 - Actions on Objectives and Goal Achievement.
sync-linear
Sync current work with Linear ticket status.
version
Show installed vs latest ai-sdlc plugin version. Bypasses the 24h SessionStart cache.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.