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 eugenepyvovarov/mcpbundler-agent-skills-marketplace --skill git-workflow-skillgit clone --depth 1 https://github.com/eugenepyvovarov/mcpbundler-agent-skills-marketplaceWrote 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/eugenepyvovarov/mcpbundler-agent-skills-marketplace/git-workflow-skill)<a href="https://agentmods.dev/skills/eugenepyvovarov/mcpbundler-agent-skills-marketplace/git-workflow-skill"><img src="https://agentmods.dev/badge/skills/eugenepyvovarov/mcpbundler-agent-skills-marketplace/git-workflow-skill/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/eugenepyvovarov/mcpbundler-agent-skills-marketplace/git-workflow-skill"><img src="https://agentmods.dev/badge/skills/eugenepyvovarov/mcpbundler-agent-skills-marketplace/git-workflow-skill.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.00065 | $0.00829 |
| Opus 5 | $0.00032 | $0.00415 |
| Sonnet 5 | $0.00013 | $0.00166 |
| Haiku 4.5 | $0.00006 | $0.00083 |
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 12d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Workflow Skill
Expert patterns for Git version control: branching, commits, collaboration, and CI/CD.
Expertise Areas
- Branching: Git Flow, GitHub Flow, Trunk-based development
- Commits: Conventional Commits, semantic versioning
- Collaboration: PR workflows, code review, merge strategies, thread resolution
- CI/CD: GitHub Actions, GitLab CI, branch protection
Reference Files
Detailed documentation for each area:
| Reference | When to Load |
|---|---|
references/branching-strategies.md |
Managing branches, choosing branching model |
references/commit-conventions.md |
Writing commits, semantic versioning |
references/pull-request-workflow.md |
Creating/reviewing PRs, thread resolution, merging |
references/ci-cd-integration.md |
CI/CD automation, GitHub Actions |
references/advanced-git.md |
Rebasing, cherry-picking, bisecting |
references/github-releases.md |
Release management, immutable releases |
Explicit Content Triggers
When creating pull requests, load references/pull-request-workflow.md for PR structure, size guidelines, and template patterns.
When reviewing PRs or responding to review comments, load references/pull-request-workflow.md for review comment levels (blocking/suggestion/nit) and the code review checklist.
When replying to PR review threads or resolving threads, load references/pull-request-workflow.md for the GraphQL API patterns for thread replies and resolution.
When merging PRs, load references/pull-request-workflow.md for the merge requirements checklist (resolved threads, Copilot review, rebased branch, CI checks).
When merging in repos requiring signed commits with rebase-only strategy, load references/pull-request-workflow.md for the local fast-forward merge workflow.
When handling merge conflicts, load references/pull-request-workflow.md for conflict resolution strategies.
When choosing a branching strategy, load references/branching-strategies.md for Git Flow, GitHub Flow, and Trunk-based patterns.
What ships with it
8 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.
- checkpoints.yaml 5.1 KB
- references/advanced-git.md 9.8 KB
- references/branching-strategies.md 8.5 KB
- references/ci-cd-integration.md 13 KB
- references/commit-conventions.md 9.7 KB
- references/github-releases.md 6.5 KB
- references/pull-request-workflow.md 15 KB
- scripts/verify-git-workflow.sh 7.3 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.
- 12d ago First seen · 94 lines · 65 tokens per session scan A f8f25f4f1438
git-workflow is a skill published in the GitHub repository eugenepyvovarov/mcpbundler-agent-skills-marketplace (12 stars, last pushed 6mo ago), licensed MIT. It adds 65 tokens to every session and 829 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-08-30.
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.
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.
git-workflow
Use for branching, committing, history repair, and release hygiene. Covers atomic commits, rebase versus merge, bisect, reflog recovery, and undoing mistakes safely.
mx-pr
Draft a pull request from the feature spec and git log, run an autonomous commit-history cleanup (content check), then publish to GitHub or GitLab (Bitbucket experimental) — or hand off. Use when a feature branch is ready for PR, standalone or from mx-flow. Usage: /mx-pr [name].