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-pr-createnpx skills add byx-darwin/gitflow-cli --skill gf-pr-creategit clone --depth 1 https://github.com/byx-darwin/gitflow-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.00046 | $0.01643 |
| Opus 5 | $0.00023 | $0.00822 |
| Sonnet 5 | $0.00009 | $0.00329 |
| Haiku 4.5 | $0.00005 | $0.00164 |
Grade A, and why
gf-pr-create 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.
How it starts
The opening of the file, as written. The whole thing — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gf-pr-create
Validates branch state, collects title/description, invokes gf pr create, returns the new PR URL. Does not review, approve, merge, or close PRs.
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
When to Use
| English | 中文 | Context |
|---|---|---|
| create a PR | 创建 PR | feature/fix branch ready |
| submit for review | 提交供审查 | pushed, awaiting reviewer |
| draft PR | 草稿 PR | work-in-progress |
| merge request | 合并请求 | GitLab terminology |
When NOT to Use
| Scenario | Why Not | Use Instead |
|---|---|---|
| Reviewing or approving a PR | This skill creates PRs, not reviews them | /gf-pr-review for overall code review and verdict |
| Merging or closing a PR | This skill only creates PRs, not manages lifecycle | /gf-pr for merge/close/reopen operations |
| Applying review feedback | This skill handles creation, not post-review fixes | /gf-pr-apply-feedback for addressing reviewer comments |
| Creating from a protected branch | This skill validates and refuses protected branch creation | Rebase onto a feature branch first |
| Checking CI/CD pipeline status | This skill validates branch state, not pipeline health | /gf-pipeline-analyzer for CI/CD analysis |
Core Pattern
command -v gf && gf auth status
git rev-parse --is-inside-work-tree
git branch --show-current
git rev-parse --abbrev-ref @{u}
git merge-base --is-ancestor origin/main HEAD
gf pr create -t "<title>" -b "<body>" -H <head> -B <base> [--draft]
Quick Reference
| Goal | Command |
|---|---|
| Create | gf pr create -t "<t>" -b "<b>" -H <head> -B <base> [--draft] |
| Push upstream | git push -u origin <branch> |
| Rebase | git rebase origin/<base> |
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 · 199 lines · 46 tokens per session scan A a0f5f99d101a
gf-pr-create is a skill published in the GitHub repository byx-darwin/gitflow-cli (2 stars, last pushed 2d ago), licensed MIT. It adds 46 tokens to every session and 1,643 once invoked, about $0.0002 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…