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/byx-darwin/gitflow-cli/gf-release-helpernpx skills add byx-darwin/gitflow-cli --skill gf-release-helpergit clone --depth 1 https://github.com/byx-darwin/gitflow-cliWrote 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/byx-darwin/gitflow-cli/gf-release-helper)<a href="https://agentmods.dev/skills/byx-darwin/gitflow-cli/gf-release-helper"><img src="https://agentmods.dev/badge/skills/byx-darwin/gitflow-cli/gf-release-helper.svg" alt="Measured on agentmods" 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 | $0.00056 | $0.01246 |
| Opus 5 | $0.00028 | $0.00623 |
| Sonnet 5 | $0.00011 | $0.00249 |
| Haiku 4.5 | $0.00006 | $0.00125 |
Grade A, and why
gf-release-helper 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 3d 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.
gf-release-helper — Semantic Release Helper
Automates: determine next version → generate changelog → create release → output URL. Full reference: docs/references/gf-release-helper-params.md
CLI Requirement
MUST use gf CLI, NOT gh CLI.
| CLI | Scope | Platform Support |
|---|---|---|
gf |
This project | GitHub + GitLab + GitCode |
gh |
GitHub only | GitHub only |
Why: gf is the unified CLI for this project. Using gh breaks GitLab/GitCode compatibility.
Preconditions
gfinstalled:command -v gfgfauthenticated:gf auth status
Overview
Infers the next SemVer version from conventional commits, generates a changelog, and creates the release.
Trigger Keywords
CN 发布 release 版本号 changelog 打标签
EN create release bump version semantic version release notes tag major minor
CLI gf release-helper <subcommand>
When NOT to Use
| Scenario | Why Not | Use Instead |
|---|---|---|
| Managing existing Release metadata (edit/delete/list) | This skill creates new releases with auto-generated changelogs | /gf-release for Release CRUD operations |
| Deleting a release | This skill only creates releases, never deletes them | /gf-release for release deletion (with double-confirm) |
| Deciding version without user confirmation | This skill infers SemVer but always requires user approval | Non-negotiable — version must be confirmed interactively |
| Publishing without showing release notes | This skill requires user review of changelog before creation | Non-negotiable — always show release notes first |
| Creating Git tags | This skill assumes tags exist or creates them as part of release flow | git tag + git push --tags for tag-only operations |
| Running release without CI verification | Releasing without confirming CI status risks broken releases | /gf-pipeline-analyzer to verify pipeline health first |
Version Decision Flow
flowchart TD
U[User wants to release] --> A{Tag exists?}
A -->|no tag| B[Initialize v0.1.0 or v1.0.0]
A -->|has tag| C[git describe --tags --abbrev=0]
C --> D[git log <last-tag>..HEAD --pretty=format:'%h %s']
D --> E{Classify commit types}
E -->|feat! / BREAKING CHANGE| MAJOR[Major X+1.0.0]
E -->|feat without breaking| MINOR[Minor x.Y+1.0]
E -->|only fix/perf/refactor| PATCH[Patch x.y.Z+1]
MAJOR --> CONFIRM[User confirms version]
MINOR --> CONFIRM
PATCH --> CONFIRM
CONFIRM --> GEN[Generate grouped changelog]
GEN --> REVIEW[User reviews]
REVIEW --> CREATE[release create --tag <v> --notes '...']
CREATE --> OUT[Output Release URL]
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.
- 3d ago First seen · 136 lines · 56 tokens per session scan A 3dd0e2f0a221
gf-release-helper is a skill published in the GitHub repository byx-darwin/gitflow-cli (2 stars, last pushed today), licensed MIT. It adds 56 tokens to every session and 1,246 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…