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 byx-darwin/gitflow-cli --skill gf-workflow-batchgit 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-workflow-batch)<a href="https://agentmods.dev/skills/byx-darwin/gitflow-cli/gf-workflow-batch"><img src="https://agentmods.dev/badge/skills/byx-darwin/gitflow-cli/gf-workflow-batch/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/byx-darwin/gitflow-cli/gf-workflow-batch"><img src="https://agentmods.dev/badge/skills/byx-darwin/gitflow-cli/gf-workflow-batch.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00096 | $0.02406 |
| Opus 5.5 | $0.00038 | $0.00962 |
| Sonnet 5.5 | $0.00019 | $0.00481 |
| Haiku 4.5 | $0.00010 | $0.00241 |
Grade A, and why
gf-workflow-batch 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 26d 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gf-workflow-batch
Serial outer driver for gf-workflow. Dispatches one fresh subagent per open
Issue via the Agent tool (never fork), blocks until it finishes
(including its Gate 2→3 approval pause), records a one-line summary, then
re-derives the next Issue from disk. Never modifies gf-workflow itself.
CLI Requirement
MUST use gf CLI, NOT gh CLI. gf is the unified multi-platform CLI
for this project (GitHub + GitLab + GitCode); gh is GitHub-only.
Preconditions
gfinstalled:command -v gfgfauthenticated:gf auth statussuperpowers:brainstormingandgf-issue-createavailable (needed only whenpendingis empty — see Discussion Mode below)
When to Use
| English | 中文 | Trigger Context |
|---|---|---|
| batch process issues | 批量处理 issue | multiple open Issues need full gf-workflow runs |
| run gf-workflow on all open issues | 对所有 open issue 跑 gf-workflow | user wants serial end-to-end automation |
| process the issue backlog | 处理 issue 积压 | backlog clearing, one Issue at a time |
| decompose this into issues | 把这个拆成多个 issue | no pending Issue, user has a large ask |
Trigger Keywords
| English | 中文 |
|---|---|
| batch workflow | 批量工作流 |
| process all issues | 处理所有 issue |
| serial driver | 串行驱动器 |
When NOT to Use
| Scenario | Why Not | Use Instead |
|---|---|---|
| Analyzing a single Issue's requirement quality | This skill dispatches /gf-workflow, it does not analyze requirements |
/gf-issue-review for requirement completeness analysis |
| Bulk classifying/labeling open Issues | This skill runs the full four-phase gate per Issue, not classification | /gf-issue-triage for bulk type/priority classification |
Core Pattern
gf issue list --state open --output json
# pending = open issues NOT covered by any active/*.json (status != complete)
# NOR by any archive/**/*.json contract
# ready = pending Issues whose `Blocked by: #N` refs are all closed
# (parsed from all open Issues' bodies; missing ref or a cycle
# aborts the whole run — see references.md § Dependency Resolution)
# if pending empty → Discussion Mode (see references.md)
# else → dispatch Agent(prompt: "/gf-workflow #<n>") for ready[0], serially
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 26d ago Changed · +33 lines ace41c3d6af5
- 1mo ago First seen · 139 lines · 96 tokens per session scan A 193f7442a3c3
gf-workflow-batch is a skill published in the GitHub repository byx-darwin/gitflow-cli (3 stars, last pushed 22d ago), licensed MIT. It adds 96 tokens to every session and 2,406 once invoked, about $0.0004 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-04.
Other skills, from other repositories
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…