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/ffroliva/gflow-cli/releasenpx skills add ffroliva/gflow-cli --skill releasegit clone --depth 1 https://github.com/ffroliva/gflow-cliWhat 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.00026 | $0.03404 |
| Opus 5 | $0.00013 | $0.01702 |
| Sonnet 5 | $0.00005 | $0.00681 |
| Haiku 4.5 | $0.00003 | $0.00340 |
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 yesterday.
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 — 280 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.
- yesterday First seen · 280 lines · 26 tokens per session scan A 5059057dfa2c
release is a skill published in the GitHub repository ffroliva/gflow-cli (136 stars, last pushed yesterday), licensed MIT. It adds 26 tokens to every session and 3,404 once invoked, about $0.0001 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-30.
Other skills, from other repositories
repomix
Pack and analyze codebases into AI-friendly single files using Repomix. Use when the user wants to explore repositories, analyze code structure, find patterns, check token counts, or prepare codebase context for AI analysis. Supports both local directories and remote GitHub repositories.
agent-carnet
Use this skill when the user asks to save, recall, find, or organize notes. Triggers on: 'remember this', 'save this', 'note this', 'what did we discuss about...', 'check the notebook', 'find in carnet'. Also use proactively when discovering findings worth preserving across sessions.
graph-mutation-plan
Cookbook for composing an applygraphmutations plan — stable entitykey patterns, the canonical label/edge vocabulary, evidence/invalidation/confidence discipline, and a worked example. Load this when building a non-trivial mutation plan.
muapi-media-editing
Edit and enhance images and videos with AI via muapi.ai — prompt-based editing, upscaling, background removal, face swap, lipsync, video effects, and more.
oracle
Best practices for using the oracle CLI (prompt + file bundling, engines, sessions, and file attachment patterns).
plano-filter-guardrails
Harden Plano filter chains and guardrails. Use for MCP filter setup, prompt guard responses, and safe filter ordering.