A four-step workflow for clarifying a task, planning it, carrying it out, and delivering the result. It records progress as JSON and requires checks between steps.

Use it to run structured coding tasks that need a documented plan, controlled handoffs, and checks before each phase continues.

It prevents work from skipping required stages or moving ahead before earlier agreements are verified.

gf-workflow — Skill by byx-darwin

Install

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.

agentmods

npx agentmods add skills/byx-darwin/gitflow-cli/gf-workflow

Any agent

npx skills add byx-darwin/gitflow-cli --skill gf-workflow

Clone the repo

git clone --depth 1 https://github.com/byx-darwin/gitflow-cli

Made for: Claude Code, Codex.

Per session 63 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 7,691 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00063	$0.07691
Opus 5	$0.00032	$0.03846
Sonnet 5	$0.00013	$0.01538
Haiku 4.5	$0.00006	$0.00769

Measured 2d ago against content hash 7d0475677fbf, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

gf-workflow 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 2d 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.

skills/gf-workflow/SKILL.md · 458 lines

How it starts

The opening of the file, as written. The whole thing — 458 lines — stays where its author put it; the contents beside it link to each section on GitHub.

gf-workflow — Contract-Driven Four-Phase Gated Orchestrator

Orchestrator commands only; state lives in the contract; gates are never skipped.

⚠️ ORCHESTRATOR MANDATE

This skill is an ORCHESTRATOR, not a sub-skill. When invoked, it drives a four-phase pipeline end-to-end. The orchestrator retains control at all times. Sub-skills (brainstorming, writing-plans, subagent-driven-development, etc.) are called and return — they do NOT take over the conversation.

Violating the letter of these rules is violating the spirit of these rules. No "I'm following the spirit" rationalizations. The rules are explicit for a reason.

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

gf installed: command -v gf
gf authenticated: gf auth status

Core Rule: Contract First

Before ANY phase executes, the orchestrator MUST:

Check for active contracts — list .cache/workflows/active/*.json
- Incomplete workflow exists (status != "complete") → RESUME it: read current_phase, load context, continue from next step
- Multiple exist → ask user which to resume
- None exist → proceed to step 2
Run mode auto-detection (full / standard / fast)
Detect skill source — see ## Skill Source Resolution. Runs BEFORE the contract exists; if both sources are absent the user chooses inline-continue or abort (abort → no contract)
Create the contract file at .cache/workflows/active/<workflow_id>.json (schema: contract.schema.json), then record skill_source via jq immediately after creation
Announce the workflow start with: workflow_id, mode, title, skill_source

If no contract exists, no sub-skill may be invoked. The contract is the single source of truth for the workflow's state.

Read the full file on GitHub · 458 lines

Files

What ships with it

3 files 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.

Changes

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.

2d ago First seen · 458 lines · 63 tokens per session scan A 7d0475677fbf

Subscribe to this mod's changes

gf-workflow is a skill published in the GitHub repository byx-darwin/gitflow-cli (2 stars, last pushed 2d ago), licensed MIT. It adds 63 tokens to every session and 7,691 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.

Planning Productivity

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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.

obra/superpowers · 37 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

agent-host-chat-contributions

Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.

microsoft/vscode · 56 tokens

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.

microsoft/vscode · 62 tokens