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-label-statsnpx skills add byx-darwin/gitflow-cli --skill gf-label-statsgit 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-label-stats)<a href="https://agentmods.dev/skills/byx-darwin/gitflow-cli/gf-label-stats"><img src="https://agentmods.dev/badge/skills/byx-darwin/gitflow-cli/gf-label-stats.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.00060 | $0.01352 |
| Opus 5 | $0.00030 | $0.00676 |
| Sonnet 5 | $0.00012 | $0.00270 |
| Haiku 4.5 | $0.00006 | $0.00135 |
Grade A, and why
gf-label-stats 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 3d 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gf-label-stats
Read-only label analytics. Queries gf label list, then gf issue list --label per label and per priority. Produces a unified report: label group counts, priority distribution with health indicators, and unclassified Issue identification. Propose fixes — never mutate.
See full label taxonomy for canonical label category reference.
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 |
|---|---|---|
| show label statistics | 显示标签统计 | health check |
| label distribution | 标签分布 | backlog grooming |
| unclassified issues | 未分类 Issue | triage backlog |
| triage all unclassified | 对所有未分类 triage | NOT → gf-issue-triage |
| delete unused label | 删除无用标签 | NOT — read-only skill |
| modify issue labels | 修改标签 | NOT → gf-issue-triage |
When NOT to Use
| Scenario | Why Not | Use Instead |
|---|---|---|
| Applying labels to Issues | This skill is strictly read-only analytics | /gf-issue-triage for batch Issue classification and labeling |
| Creating or editing label definitions | This skill reads label data, not manages label metadata | /gf-label-milestone for label/milestone CRUD |
| Analyzing a single Issue's requirements | This skill analyzes label distribution across all Issues | /gf-issue-review for individual Issue requirement review |
| Deleting unused labels | This skill never mutates labels or Issues | /gf-label-milestone for label deletion |
| Estimating Issue counts | This skill uses exact CLI output only, never estimates | Run gf issue list --label directly for counts |
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.
- 3d ago First seen · 152 lines · 60 tokens per session scan A 12493549b18c
gf-label-stats is a skill published in the GitHub repository byx-darwin/gitflow-cli (2 stars, last pushed 3d ago), licensed MIT. It adds 60 tokens to every session and 1,352 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
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
sap-transport-overview
System-wide inventory of open transport requests — every visible modifiable request, who owns it, how big it is, and supported risk signals such as empty/local requests, explicit locks, and confirmed manifest overlaps. Headers-only and cheap; NO source diffs. Use when asked "what transports are open in the system"…
timeline-creator
Create HTML timelines and project roadmaps with Gantt charts, milestones, phase groupings, and progress indicators. Use when users request timelines, roadmaps, Gantt charts, project schedules, or milestone visualizations.
pm-all
Skill "pm-all" from wei63w/pm-manager, covering user input, outline and shared workflow (all /pm- commands).
bootstrap-prd
Set up PRD-driven development infrastructure for a new project, including directory structure, templates, and roadmap.
finn-spec
Interview the user about a raw idea until confident, then file a build-ready issue in Linear. Use when asked to run Finn-loop's spec interview, draft a queue-ready issue, or plan a feature. Interactive — requires the user present; never run unattended.