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 skills/soulcodex/agentic/git-flow-prnpx skills add soulcodex/agentic --skill git-flow-prgit clone --depth 1 https://github.com/soulcodex/agenticWhat 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.00103 | $0.01872 |
| Opus 5 | $0.00051 | $0.00936 |
| Sonnet 5 | $0.00021 | $0.00374 |
| Haiku 4.5 | $0.00010 | $0.00187 |
Grade A, and why
git-flow-pr 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 2d 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 — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Flow PR Skill
Complete workflow for creating a clean, rebased pull request from in-progress work.
Step 1 — Confirm Current State
Before doing anything, understand what exists:
git status --short # Are there uncommitted changes?
git log --oneline -10 # What commits exist on this branch?
git branch --show-current # Which branch are we on?
BASE_BRANCH="<base-branch>" # e.g. main, develop, release/*
git fetch origin "$BASE_BRANCH"
git log --oneline "origin/$BASE_BRANCH"..HEAD # Commits unique to this branch
Identify:
- The base branch (often
main, but use the repo's actual target) - Any uncommitted changes that need to be staged
- Whether the current branch's ancestor commits are already merged into main
(this determines which
--ontostrategy to use in Step 4)
Step 2 — Stage and Commit (if uncommitted changes exist)
If there are uncommitted changes, stage and commit them now:
git add <files> # Stage relevant files; be specific — don't `git add .` blindly
git commit -m "<type>(<scope>): <summary>
<body explaining why, not just what>
Closes #<issue-number>"
Commit message rules:
- Follow Conventional Commits:
feat,fix,docs,chore,refactor,test - Scope should reflect the area changed:
(gemini),(tooling),(docs),(skills), etc. - For final PRs that should auto-close the issue on merge, use
Closes #NorFixes #N - For stacked/chained PRs or partial work, use
Refs #Nto link without auto-closing - Keep the subject line ≤ 72 characters
Step 3 — Create the Feature Branch
Create a new branch from the tip of the current work and give it a descriptive name:
COMMIT=$(git rev-parse HEAD)
git checkout -b feat/<short-description> "$COMMIT"
Branch naming convention:
feat/<description>— new feature or enhancementfix/<description>— bug fixdocs/<description>— documentation onlychore/<description>— maintenance, tooling, dependencies
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.
- 2d ago First seen · 221 lines · 103 tokens per session scan A 0f24515b467a
git-flow-pr is a skill published in the GitHub repository soulcodex/agentic (10 stars, last pushed 2d ago), licensed MIT. It adds 103 tokens to every session and 1,872 once invoked, about $0.0005 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-31.
Other skills, from other repositories
github-cli
Automate GitHub workflows using the gh CLI for pull requests, issues, releases, actions, and repository management. Use when interacting with GitHub beyond basic git operations.
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts) and an annotated tag. Verify, commit, tag. Stops at "committed and tagged locally" — no push, no publish. The release-and-publish skill picks up from here. Distilled…
git-workflow
Git operations: commits, branches, PRs, and conflict resolution.
github
Prepare GitHub issues, pull requests, reviews, and release notes for Zhin projects. Use when asked to write an issue, PR description, changelog entry, or review comment. Triggers: 写 issue, PR 描述, 提 PR, release notes, gh pr.
ship
Commit, push, create PR, then after approval check CI and merge. Use when work is done and ready to ship.
git-workflows
Use when thinking through, reviewing, changing, or verifying Git repositories and version-control workflows: branches, commits, merges, rebases, cherry-picks, conflicts, worktrees, remotes, pull requests, protected refs, force pushes, tags, semantic versions, release branches, history rewrites, secret removal, merge…