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-triagenpx skills add byx-darwin/gitflow-cli --skill gf-issue-triagegit 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-triage)<a href="https://agentmods.dev/skills/byx-darwin/gitflow-cli/gf-issue-triage"><img src="https://agentmods.dev/badge/skills/byx-darwin/gitflow-cli/gf-issue-triage.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.00056 | $0.01779 |
| Opus 5 | $0.00028 | $0.00890 |
| Sonnet 5 | $0.00011 | $0.00356 |
| Haiku 4.5 | $0.00006 | $0.00178 |
Grade A, and why
gf-issue-triage 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 today.
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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gf-issue-triage
Batch classification of all open Issues — assigns one type:* label and one priority:* label per Issue, then marks triage:done. Outputs a priority-ranked report. Idempotent — skip already-triaged Issues.
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 |
|---|---|---|
| triage all issues | 对全部分类 | backlog grooming |
| classify issues | 分类 Issue | sprint planning |
| new issues since ... | 对近期新增分类 | --since flag |
| analyze an issue's requirement | 分析需求质量 | NOT → /gf-issue-review |
| label statistics | 标签统计 | NOT → /gf-label-stats |
When NOT to Use
| Scenario | Why Not | Use Instead |
|---|---|---|
| Analyzing a single Issue's requirement quality | This skill batch-classifies all open Issues, not deep analysis of one | /gf-issue-review for three-dimension requirement review |
| Viewing label distribution statistics | This skill applies labels, not analyzes their distribution | /gf-label-stats for read-only label analytics |
| Creating or editing label definitions | This skill assigns labels to Issues, not manages label metadata | /gf-label-milestone for label CRUD |
| Creating a new Issue | This skill classifies existing Issues only | /gf-issue-create for Issue creation |
| Editing Issue body text | This skill only adds labels, never modifies Issue content | /gf-issue for edit operations |
Core Pattern
gf issue list --state open [--since <date>]
gf issue add-label <n> --label "type:<t>" --label "priority:<p>" --label "triage:done"
Quick Reference
| Goal | Command |
|---|---|
| List open | gf issue list --state open [--since <date>] |
| Add label | gf issue add-label <n> --label "<l>" |
| Filter by label | gf issue list --label "<l>" --state open |
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.
- today Changed · +9 lines cc57d6e9aee7
- 4d ago First seen · 185 lines · 56 tokens per session scan A 4e95534aa85a
gf-issue-triage is a skill published in the GitHub repository byx-darwin/gitflow-cli (2 stars, last pushed today), licensed MIT. It adds 56 tokens to every session and 1,779 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…