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-reviewnpx skills add byx-darwin/gitflow-cli --skill gf-pr-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-pr-review)<a href="https://agentmods.dev/skills/byx-darwin/gitflow-cli/gf-pr-review"><img src="https://agentmods.dev/badge/skills/byx-darwin/gitflow-cli/gf-pr-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.00046 | $0.01651 |
| Opus 5 | $0.00023 | $0.00826 |
| Sonnet 5 | $0.00009 | $0.00330 |
| Haiku 4.5 | $0.00005 | $0.00165 |
Grade A, and why
gf-pr-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 4d 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-review
6-dimension PR diff assessment + overall verdict via gf review. Line-level comments → gf-pr-inline-review.
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 |
|---|---|---|
| review PR | 审查 PR | overall verdict |
| approve / LGTM | 审批 / 通过 | post-analysis |
| request changes | 要求修改 | PR blocked |
| inline / line review | 逐行评论 | → gf-pr-inline-review |
| merge / close | 合并/关闭 | → gf-pr |
When NOT to Use
| Scenario | Why Not | Use Instead |
|---|---|---|
| Leaving line-level inline comments | This skill submits an overall verdict, not per-line comments | /gf-pr-inline-review for line-level inline review |
| Applying review fixes to code | This skill assesses code and submits verdict, not modifies source | /gf-pr-apply-feedback for applying fixes |
| Merging or closing the PR | This skill submits review verdicts, not lifecycle operations | /gf-pr for merge/close/reopen |
| Creating a Pull Request | This skill reviews existing PRs only | /gf-pr-create for PR creation workflow |
| Deep security vulnerability scanning | This skill includes security as one of 6 dimensions, not a full audit | /gf-security-check for comprehensive security audit |
| Submitting verdict without reading diff | This skill requires full diff analysis before verdict | Non-negotiable — always read diff first |
Core Pattern
gf pr view <n> # 1. verify
gf pr diff <n> # 2. diff
# 3. assess 6 dims; draft conclusion
gf review approve <n> --body "<c>" # 4. submit (or request-changes / comment)
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.
- 4d ago First seen · 199 lines · 46 tokens per session scan A ae80c64c76c9
gf-pr-review is a skill published in the GitHub repository byx-darwin/gitflow-cli (2 stars, last pushed yesterday), licensed MIT. It adds 46 tokens to every session and 1,651 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…
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…