Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/ffroliva/gflow-clinpx agentmods add skills/ffroliva/gflow-cli/releaseWrote 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/ffroliva/gflow-cli/release)<a href="https://agentmods.dev/skills/ffroliva/gflow-cli/release"><img src="https://agentmods.dev/badge/skills/ffroliva/gflow-cli/release/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/ffroliva/gflow-cli/release"><img src="https://agentmods.dev/badge/skills/ffroliva/gflow-cli/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 258 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00026 | $0.05337 |
| Opus 5.5 | $0.00010 | $0.02135 |
| Sonnet 5.5 | $0.00005 | $0.01067 |
| Haiku 4.5 | $0.00003 | $0.00534 |
Grade A, and why
release 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 today.
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 — 406 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/gflow:release — Cut a new release
Follow this sequence verbatim. Every step matters.
Branch-protection note:
mainblocks direct pushes. The release commit travels via achore/release-vX.Y.Zbranch PR. The signed tag is pushed independently (tag pushes bypass branch protection and trigger the CI release workflow immediately).Source-branch note (read first):
developis the integration branch — it carries ALL unreleased work andmainusually lags it. The release branch is cut fromdevelop, NOTmain. The PRchore/release-vX.Y.Z → mainthen brings the full integration history ontomain. Do not expect the work to already be onmain.
Inputs
Ask the user (if not already provided):
- Version — the new version (e.g.
0.4.0,0.4.0a3,1.0.0rc1). Use PEP 440 prerelease suffixes (aN,bN,rcN). If they don't know, run/gflow:changelogfirst and propose the next bump (PATCH for fixes only, MINOR for new features, MAJOR for breaks). - Pre-release? — prerelease versions stay marked as GitHub prereleases. Only the user can say when a release line is ready for the stable tag.
Sequence
1. Review what's queued.
Run /gflow:changelog — confirm the [Unreleased] block is non-empty and accurate before proceeding.
2. Verify (or triage) a clean working tree.
git status --short
If empty, continue. If not, triage before aborting — do not blindly stop:
- Auto-injected boilerplate (e.g. a context-mode routing block appended to
CLAUDE.mdby an MCP plugin's SessionStart hook): this is plugin-injected, not project content —git restoreit. Confirm with the user if unsure. - Build/temp artifacts (e.g. a stray
tmp*.tar.gzsdist at repo root): delete them. - Genuine uncommitted work: STOP and tell the user to commit or stash on the
appropriate branch (never commit straight to
develop).
The tree must be clean before you create the release branch.
3. Verify develop is the release source and up-to-date.
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.
- today Changed · +2 lines fd7c0bc34116
- 1mo ago Changed · +30 lines 533226a3d3b0
- 1mo ago Changed · +3 lines 8b2eb195cf33
- 1mo ago Changed · +69 lines f688237c847a
- 1mo ago Changed · +22 lines d001e3efc395
- 1mo ago First seen · 280 lines · 26 tokens per session scan A 5059057dfa2c
release is a skill published in the GitHub repository ffroliva/gflow-cli (309 stars, last pushed today), licensed MIT. It adds 26 tokens to every session and 5,337 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-08-30.
Other skills, from other repositories
bump-version
A release procedure for termio, a macOS app, that creates a numbered Git tag on the main branch. A Git tag is a permanent label for a specific version of the code.
testflight-release
Ship a new TestFlight build of the iOS companion (TermioMobile) — resolve the next build number against App Store Connect, archive, sign, export, upload, write the What to Test notes, and distribute. Invoke when the user says 'ship a testflight build', 'update testflight', 'upload to testflight', 'new beta build'…
hatch3r-release
Cuts a release with version bump, changelog, tagging, and deploy verification. Use when preparing a release, cutting a version, or deploying to production.
git-flow-pr
Executes the full PR-driven development workflow: create an isolated feature branch from the current work, commit all staged changes, rebase cleanly onto the selected base branch (skipping any ancestor commits already merged), push the branch, and open a GitHub pull request linked to a related issue. Includes guidance…
write-changelog
Generates a CHANGELOG.md entry for a release by summarizing git commits since the last tag. Groups changes by type: Added, Changed, Fixed, Removed. Follows Keep a Changelog format (https://keepachangelog.com). Invoked when the user asks to update the changelog, write release notes, or prepare a release.
hatch3r-cli-gh
GitHub CLI — repos, issues, PRs, releases, gists. Use when drafting GitHub pull requests, issues, releases, gists, or workflow dispatches; invoke gh. Authenticates via the platform's native token mechanism (OAuth / PAT).