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 JHostalek/dotclaude --skill git-workflowgit clone --depth 1 https://github.com/JHostalek/dotclaudeWrote 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/jhostalek/dotclaude/git-workflow)<a href="https://agentmods.dev/skills/jhostalek/dotclaude/git-workflow"><img src="https://agentmods.dev/badge/skills/jhostalek/dotclaude/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/jhostalek/dotclaude/git-workflow"><img src="https://agentmods.dev/badge/skills/jhostalek/dotclaude/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.00030 | $0.00296 |
| Opus 5.5 | $0.00012 | $0.00118 |
| Sonnet 5.5 | $0.00006 | $0.00059 |
| Haiku 4.5 | $0.00003 | $0.00030 |
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 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.
What it actually says
Use the mode requested by the user or calling skill. A request for a commit message only produces a message; an ordinary commit or PR request does not authorize merging. Honor narrower instructions already given.
Read the relevant reference before acting:
| Mode | Reference |
|---|---|
| Commit or commit message | commit.md |
| Create or update a PR/MR | pr.md |
| Merge a branch, rebase, or resolve conflicts | integration.md |
| Explicit end-to-end shipping | ship.md |
Use the intended repository, current branch, and remote. Preserve unrelated work and staged changes. One PR per repository; update an existing PR for the branch.
Ordinary commit mode commits locally. PR mode includes pushing the relevant commits. Explicit branch-merge and rebase modes include publishing the result, using a lease for a rewritten remote branch. End-to-end mode includes implementation, verification, commit, push, PR creation/update, merge, and remote source-branch deletion.
Report the completed operation, relevant commit or PR, verification, and any unresolved blocker. Publishing and merging are complete only when the remote confirms them.
What ships with it
6 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.
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 Changed 0b168147a8f6
- 1mo ago First seen · 23 lines · 30 tokens per session scan A c647b7d90c38
git-workflow is a skill published in the GitHub repository JHostalek/dotclaude (11 stars, last pushed 3d ago), licensed CC0-1.0. It adds 30 tokens to every session and 296 once invoked, about $0.0001 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-06.
Other skills, from other repositories
what-did-i-get-done
Summarize authored commits over a user-specified time period into a concise update.
memstack-security-git-guard
Use when the user says 'git-guard', 'check git protection', 'is this repo protected', 'verify gitleaks', 'set up git hooks', 'install git-guard', or wants to confirm a repo blocks secrets and internal files before commit. This is an installer and verifier, NOT a scanner (gitleaks does the actual scanning). Do NOT use…
ln-61-repository-publisher
Commits, pushes and remotely verifies authorized repository changes; does not create releases.
git-workflow
Git conventions and workflow guidelines using Conventional Commits, branching strategies, and best practices for version control.
github-workflow
GitHub best practices for pull requests, code reviews, issues, Actions workflows, and repository management.
lerna
Best practices for Lerna monorepo management, versioning, and publishing.