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-issue-reviewnpx skills add byx-darwin/gitflow-cli --skill gf-issue-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-issue-review)<a href="https://agentmods.dev/skills/byx-darwin/gitflow-cli/gf-issue-review"><img src="https://agentmods.dev/badge/skills/byx-darwin/gitflow-cli/gf-issue-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.00066 | $0.01591 |
| Opus 5 | $0.00033 | $0.00796 |
| Sonnet 5 | $0.00013 | $0.00318 |
| Haiku 4.5 | $0.00007 | $0.00159 |
Grade A, and why
gf-issue-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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gf-issue-review
Three-dimensional Issue requirement review — title clarity / description sufficiency / acceptance criteria — emits a structured analysis report, then posts it as an Issue comment. Does not edit the Issue itself.
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 the requirement | 审查需求质量 | check description completeness |
| is this issue clear enough | 这个 Issue 描述够吗 | before triage/triage |
| improve issue description | 改进 Issue 描述 | before development |
| triage this issue | 对 Issue 进行分类 | NOT → /gf-issue-triage |
When NOT to Use
| Scenario | Why Not | Use Instead |
|---|---|---|
| Batch classifying Issues by type/priority | This skill analyzes one Issue's requirement depth, not bulk classification | /gf-issue-triage for batch type+priority labeling |
| Creating a new Issue | This skill analyzes existing Issues only | /gf-issue-create for interactive Issue creation |
| Editing Issue content | This skill posts analysis as comments but never edits the Issue itself | /gf-issue for edit operations |
| Reviewing PR code | This skill reviews Issue requirements, not code diffs | /gf-pr-review for PR code review |
| Labeling Issues with statistics | This skill scores requirement quality, not label distribution | /gf-label-stats for label analytics |
Core Pattern
gf issue view <n>
# analyze 3 dimensions → write /tmp/issue-analysis.md
gf issue comment <n> --body-file /tmp/issue-analysis.md
rm -f /tmp/issue-analysis.md
Quick Reference
| Goal | Command |
|---|---|
| Fetch Issue | gf issue view <n> |
| Post comment | gf issue comment <n> --body-file <path> |
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 · 191 lines · 66 tokens per session scan A 2a6e3445a304
gf-issue-review is a skill published in the GitHub repository byx-darwin/gitflow-cli (2 stars, last pushed today), licensed MIT. It adds 66 tokens to every session and 1,591 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…