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-reviewnpx skills add byx-darwin/gitflow-cli --skill gf-reviewgit 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-review)<a href="https://agentmods.dev/skills/byx-darwin/gitflow-cli/gf-review"><img src="https://agentmods.dev/badge/skills/byx-darwin/gitflow-cli/gf-review.svg" alt="Measured on agentmods" 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 | $0.00048 | $0.01799 |
| Opus 5 | $0.00024 | $0.00899 |
| Sonnet 5 | $0.00010 | $0.00360 |
| Haiku 4.5 | $0.00005 | $0.00180 |
Grade A, and why
gf-review 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 3d 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 — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gf-review
Submits review verdicts via gf review. Read-only skill — does not analyze code, edit files, or choose verdicts. Users must run /gf-pr-review or /gf-pr-inline-review first to form verdict, or supply verdict explicitly.
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 |
|---|---|---|
| approve PR, LGTM | 批准 PR、通过了 | verdict ready |
| request changes, reject | 要求修改、驳回 | blocking issues |
| submit review | 提交审查 | after inline comments |
| code review decision | 审查决策 | formal verdict |
| merge / close | 合并/关闭 | → /gf-pr |
| review analysis | 审查分析 | → /gf-pr-review |
| inline review | 行内审查 | → /gf-pr-inline-review |
When NOT to Use
| Scenario | Why Not | Use Instead |
|---|---|---|
| Performing code analysis to form a verdict | This skill submits verdicts only, does not analyze code | /gf-pr-review for 6-dimension code analysis |
| Leaving line-level inline comments | This skill submits formal verdicts, not inline comments | /gf-pr-inline-review for per-line review comments |
| Approving without prior analysis | This skill requires prior review or explicit user-supplied verdict | Non-negotiable — always require /gf-pr-review or user verdict first |
| Reviewing your own PR | This skill prohibits self-review | Non-negotiable — refuse self-review requests |
| Merging or closing the PR | This skill submits review verdicts, not lifecycle operations | /gf-pr for merge/close/reopen |
| Auto-submitting without user confirmation | This skill requires explicit confirmation before every submission | Non-negotiable — always present verdict and await user OK |
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.
- 3d ago First seen · 200 lines · 48 tokens per session scan A 2ec7d677dadb
gf-review is a skill published in the GitHub repository byx-darwin/gitflow-cli (2 stars, last pushed 3d ago), licensed MIT. It adds 48 tokens to every session and 1,799 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…