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 Mindrally/skills --skill gitflowgit clone --depth 1 https://github.com/Mindrally/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/skills/mindrally/skills/gitflow)<a href="https://agentmods.dev/skills/mindrally/skills/gitflow"><img src="https://agentmods.dev/badge/skills/mindrally/skills/gitflow/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/mindrally/skills/gitflow"><img src="https://agentmods.dev/badge/skills/mindrally/skills/gitflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00078 | $0.01345 |
| Opus 5.5 | $0.00031 | $0.00538 |
| Sonnet 5.5 | $0.00016 | $0.00269 |
| Haiku 4.5 | $0.00008 | $0.00135 |
Grade A, and why
gitflow 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 7d 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gitflow
This skill covers the Gitflow branching model: the two long-lived branches, the three supporting branch types, commit message conventions, semantic versioning, and the release and hotfix processes.
Workflow for a Feature Change
- Sync develop — Run
git checkout develop && git pull origin developso the feature branches from the latest development state. - Create the feature branch — Run
git checkout -b feature/123-user-authentication, using the naming conventionfeature/[issue-id]-descriptive-name. - Commit with conventional messages — Use
type(scope): descriptionfor every commit (see Commit Messages below). - Rebase or merge develop in — Before opening a PR, bring the branch up to date:
git fetch origin && git rebase origin/develop(or merge, per team convention). - Open a pull request into develop — Require at least one approval and passing CI checks; never commit directly to
develop. - Merge and clean up — After merge, delete the feature branch both locally and on the remote:
git branch -d feature/123-user-authentication && git push origin --delete feature/123-user-authentication.
Main Branches
main (or master)
- Contains production-ready code only.
- Never commit directly to
main. - Only accepts merges from
hotfix/*branches orrelease/*branches. - Must be tagged with a version number after every merge (e.g.
git tag -a v1.2.0 -m "Release 1.2.0").
develop
- The main integration branch; contains the latest delivered development changes.
- Source branch for all
feature/*branches. - Never commit directly to
develop— all changes land through pull requests.
Supporting Branches
feature/*
- Branch from:
develop. - Merge back into:
develop. - Naming convention:
feature/[issue-id]-descriptive-name(e.g.feature/123-user-authentication). - Must be up to date with
developbefore opening a PR. - Delete after merge.
release/*
- Branch from:
develop. - Merge back into:
mainanddevelop. - Naming convention:
release/vX.Y.Z(e.g.release/v1.2.0). - Scope is limited to bug fixes, documentation, and release-oriented tasks — no new features.
- Delete after merge.
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.
- 7d ago Changed · +3 lines 770d41cf9548
- 1mo ago First seen · 133 lines · 78 tokens per session scan A a5419175b77a
gitflow is a skill published in the GitHub repository Mindrally/skills (276 stars, last pushed 7d ago), licensed Apache-2.0. It adds 78 tokens to every session and 1,345 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-09-03.
Other skills, from other repositories
publish
Publish oh-my-opencode to npm by triggering the GitHub Actions publish workflow and verifying its artifacts. Ship-only: never runs pre-publish-review or re-reviews merged code unless the user explicitly asks. Argument: . Triggers: publish, release, deploy, npm publish.
pre-publish-review
Nuclear-grade 12-agent pre-publish release gate. Runs /get-unpublished-changes to detect all changes since last npm release, spawns up to 10 ultrabrain agents for deep per-change analysis, invokes /review-work (orchestrator manual QA plus one gate reviewer) for holistic review, and 1 oracle for overall release…
get-unpublished-changes
Compare HEAD with the latest published npm versions and list all unpublished changes by release layer. Triggers: unpublished changes, changelog, what changed, whats new.
memstack-development-changelog-generator
Use when the user says 'generate changelog', 'update changelog', 'what changed', 'release notes', 'write changelog', or needs a formatted CHANGELOG.md from git commit history. Do NOT use for diary entries, git log viewing, or commit message writing.
suede-play-release
Suede Labs Google Play delivery skill: ship an Android release end to end from the agent interface, without opening the Play Console. Set up credentials, upload an AAB, promote between tracks, stage or complete a rollout, push per-locale release notes, and prove against the Play Developer API what is actually live.…
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.