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-commitnpx skills add byx-darwin/gitflow-cli --skill gf-commitgit 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.00048 | $0.01583 |
| Opus 5 | $0.00024 | $0.00792 |
| Sonnet 5 | $0.00010 | $0.00317 |
| Haiku 4.5 | $0.00005 | $0.00158 |
Grade A, and why
gf-commit 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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gf-commit
Encapsulates gf commit for viewing, diffing, patching, and line-commenting commits. Read-only except comment, which publishes.
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 |
|---|---|---|
| view / inspect a commit | 查看 commit | details, files changed, stats |
| diff / what changed | commit diff | unified diff |
| patch / export commit | 导出 commit | raw patch |
| comment on a commit line | 在 commit 上评论 | publish inline comment |
| fix bug in commit | 修复 bug | NOT — out of scope |
When NOT to Use
| Scenario | Why Not | Use Instead |
|---|---|---|
| Creating or fixing commits | This skill only inspects existing commits, never creates or amends them | /gf-workflow for commit creation and bug fixes |
| Reviewing a Pull Request | This skill targets standalone commits, not PR-level review | /gf-pr-review for overall PR review, /gf-pr-inline-review for line-level |
| Running pre-commit checks | This skill operates on already-pushed commits | /gf-precommit for pre-commit quality gates |
| Browsing commit history | This skill requires a specific SHA, not log exploration | git log or git rev-list for history browsing |
| Merging or approving changes | This skill has no merge/approve capability | /gf-pr for PR lifecycle operations |
Core Pattern
command -v gf && git cat-file -t <sha> # preconditions
gf commit view <sha> # verify + read
gf commit diff <sha> # diff
gf commit patch <sha> # patch
gf commit comment <sha> --body <t> --path <p> --line <n>
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 · 185 lines · 48 tokens per session scan A e29ecfa7a207
gf-commit is a skill published in the GitHub repository byx-darwin/gitflow-cli (2 stars, last pushed yesterday), licensed MIT. It adds 48 tokens to every session and 1,583 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.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…