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-issuenpx skills add byx-darwin/gitflow-cli --skill gf-issuegit 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.00064 | $0.01758 |
| Opus 5 | $0.00032 | $0.00879 |
| Sonnet 5 | $0.00013 | $0.00352 |
| Haiku 4.5 | $0.00006 | $0.00176 |
Grade A, and why
gf-issue 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 2d 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-issue
Overview
Wraps gf issue. 8 subcommands: create · list · view · close · reopen · comment · comments · label.
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
| Trigger | 中文 | Redirect |
|---|---|---|
| create / open | 创建 Issue | — |
| list / view | 列出 Issue | — |
| view / show #N | #N 详情 | — |
| close / resolve | 关闭 Issue | — |
| reopen | 重新打开 | — |
| add comment | 添加评论 | — |
| list comments / show comments | 查看评论 | — |
| add label | 添加标签 | — |
| full workflow | 全流程 | → gf-issue-create |
| analyze requirements | — | → gf-issue-review |
When NOT to Use
| Scenario | Why Not | Use Instead |
|---|---|---|
| Interactive guided Issue creation | This skill wraps raw CRUD subcommands, not the full interactive workflow | /gf-issue-create for guided title/body/label collection |
| Analyzing Issue requirement quality | This skill performs CRUD operations, not requirement analysis | /gf-issue-review for three-dimension scoring |
| Batch classifying all open Issues | This skill operates on individual Issues, not bulk triage | /gf-issue-triage for batch type+priority classification |
| Automated bug reporting | This skill requires manual command invocation | /gf-autoreport-bug for automated pending.json processing |
| Editing Issue title or description | gf issue does not support editing body fields |
Platform web UI |
| Deleting Issues | gf issue has no delete subcommand |
Platform web UI |
Core Pattern
gf issue create --title <t> --body <b> --label <l> --assignee <a>
gf issue list [--state open|closed|all] [--label <l>] [--limit <n>]
gf issue view <number>
gf issue close <number>
gf issue reopen <number>
gf issue comment <number> --body <text>
gf issue comments <number>
gf issue add-label <number> --label <l>
gf issue remove-label <number> --label <l>
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.
- 2d ago First seen · 200 lines · 64 tokens per session scan A 798c78159373
gf-issue is a skill published in the GitHub repository byx-darwin/gitflow-cli (2 stars, last pushed 2d ago), licensed MIT. It adds 64 tokens to every session and 1,758 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…