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 willvelida/code-minions --skill git-workflowgit clone --depth 1 https://github.com/willvelida/code-minionsWrote 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/willvelida/code-minions/git-workflow)<a href="https://agentmods.dev/skills/willvelida/code-minions/git-workflow"><img src="https://agentmods.dev/badge/skills/willvelida/code-minions/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/willvelida/code-minions/git-workflow"><img src="https://agentmods.dev/badge/skills/willvelida/code-minions/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.00079 | $0.00908 |
| Opus 5.5 | $0.00032 | $0.00363 |
| Sonnet 5.5 | $0.00016 | $0.00182 |
| Haiku 4.5 | $0.00008 | $0.00091 |
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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Workflow
Overview
A complete git workflow skill covering the full development lifecycle — from repository setup through release. Supports four workflow models based on team size and release cadence.
Workflow Models
1. Centralized Workflow
All developers commit directly to main. Best for small teams or SVN migrations.
- Single branch (
main) - Pull with rebase to stay linear
- Conflict resolution before push
2. Feature Branch Workflow
All development happens on dedicated branches. Core idea: main never contains broken code.
- Create a branch per feature or fix
- Open a pull request for code review
- Merge into
mainafter approval
3. Gitflow Workflow
Strict branching model designed around project releases. Extends Feature Branch with release management.
main— production-ready codedevelop— integration branch for featuresfeature/*— new features branch fromdeveloprelease/*— release preparation brancheshotfix/*— urgent fixes branch frommain
4. Forking Workflow
Each developer has their own server-side fork. Common in open source.
- Fork the upstream repository
- Clone your fork locally
- Push to your fork, open PRs against upstream
Workflow Selection Guide
| Criteria | Centralized | Feature Branch | Gitflow | Forking |
|---|---|---|---|---|
| Team size | 1–3 | 2–10 | 5+ | Any (open source) |
| Release cadence | Continuous | Continuous | Scheduled | Varies |
| Branch complexity | Minimal | Low | High | Medium |
| Code review | Optional | Required | Required | Required |
| Best for | Small teams, simple projects | Most teams | Versioned releases | Open source, external contributors |
Capabilities
| Capability | Action | Description |
|---|---|---|
| Initialize Repository | actions/initialize-repository.md |
Clone, set up remotes, or fork |
| Create Feature Branch | actions/create-feature-branch.md |
Create and push a feature branch |
| Commit Changes | actions/commit-changes.md |
Stage and commit with conventional commits |
| Sync with Upstream | actions/sync-with-upstream.md |
Pull and rebase to stay current |
| Create Pull Request | actions/create-pull-request.md |
Open a PR for code review |
| Resolve Merge Conflicts | actions/resolve-merge-conflicts.md |
Handle conflicts during rebase or merge |
| Merge Pull Request | actions/merge-pull-request.md |
Merge an approved PR into the target branch |
| Create Release | actions/create-release.md |
Create release branches and tags (Gitflow) |
| Create Hotfix | actions/create-hotfix.md |
Create and merge hotfix branches (Gitflow) |
What ships with it
14 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.
- actions/commit-changes.md 3.2 KB
- actions/create-feature-branch.md 1.7 KB
- actions/create-hotfix.md 3.4 KB
- actions/create-pull-request.md 2.7 KB
- actions/create-release.md 3.1 KB
- actions/initialize-repository.md 2.2 KB
- actions/merge-pull-request.md 3.2 KB
- actions/resolve-merge-conflicts.md 2.3 KB
- actions/sync-with-upstream.md 2.2 KB
- standards/branch-naming.md 2.1 KB
- standards/checklist.md 3.1 KB
- standards/code-review.md 2.4 KB
- standards/commit-messages.md 3.4 KB
- standards/merge-strategy.md 3.0 KB
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 · 91 lines · 79 tokens per session scan A efdc2483d4f6
git-workflow is a skill published in the GitHub repository willvelida/code-minions (23 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 79 tokens to every session and 908 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.
changelog
Auto-generate a changelog from git commits and sprint data. Internal and player-facing versions.
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.
git-workflow
Guided git workflows: prepare PRs, clean up branches, resolve merge conflicts, handle monorepo tags, squash-and-merge patterns. Use when asked to prepare a PR, clean branches, resolve conflicts, or tag a release.
git-push
A GitHub publishing workflow that handles first-time uploads, routine updates, and tagged releases. Git is a system for recording code changes, while GitHub hosts repositories and releases online.
close-task-commit-push-pr
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.