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-apply-feedbacknpx skills add byx-darwin/gitflow-cli --skill gf-pr-apply-feedbackgit 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-apply-feedback)<a href="https://agentmods.dev/skills/byx-darwin/gitflow-cli/gf-pr-apply-feedback"><img src="https://agentmods.dev/badge/skills/byx-darwin/gitflow-cli/gf-pr-apply-feedback.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.00052 | $0.01668 |
| Opus 5 | $0.00026 | $0.00834 |
| Sonnet 5 | $0.00010 | $0.00334 |
| Haiku 4.5 | $0.00005 | $0.00167 |
Grade A, and why
gf-pr-apply-feedback 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 — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gf-pr-apply-feedback
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
Overview
Fetch pending review feedback · prioritize (security → logic → boundary → naming → style) · apply per-comment fix after user confirmation · mark resolved · push + notify reviewer. Does not review or merge.
When to Use
| Trigger | 中文 | Redirect |
|---|---|---|
| apply / address / resolve feedback | 应用/处理审查反馈 | — |
| resolve comments | 解决评论 | — |
| apply / pick up review | 审查后续 | — |
| review PR initially | 初次审查 | → gf-pr-review |
| inline diff review | 行内审查 | → gf-pr-inline-review |
When NOT to Use
| Scenario | Why Not | Use Instead |
|---|---|---|
| Performing initial PR code review | This skill applies existing feedback, not generates new reviews | /gf-pr-review for initial 6-dimension code review |
| Creating a Pull Request | This skill operates on existing PRs with pending feedback | /gf-pr-create for PR creation workflow |
| Merging or closing PRs | This skill applies feedback and resolves comments, not lifecycle ops | /gf-pr for merge/close/reopen operations |
| Leaving inline review comments | This skill resolves existing comments, not creates new ones | /gf-pr-inline-review for line-level review comments |
| Rejecting or disputing reviewer feedback | This skill applies feedback with user confirmation, not debates it | Discuss with reviewer directly before applying |
| Running quality checks after fixes | This skill focuses on applying feedback per-comment | /gf-quality for full 6-gate quality verification |
Core Pattern
gf pr view <pr> # fetch + list pending
# prioritize → confirm each comment with user
git checkout <pr-branch> # confirmed PR branch
# per comment: edit → test → commit (referencing reviewer + location)
# Note: resolve comments via platform web UI (GitHub/GitLab)
git push origin <pr-branch> # ONLY after explicit confirmation
gf pr comment <pr> --body "<summary>" # notify
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 · 179 lines · 52 tokens per session scan A 86f588fd828d
gf-pr-apply-feedback is a skill published in the GitHub repository byx-darwin/gitflow-cli (2 stars, last pushed today), licensed MIT. It adds 52 tokens to every session and 1,668 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.
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…