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-milestonenpx skills add byx-darwin/gitflow-cli --skill gf-label-milestonegit 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-milestone)<a href="https://agentmods.dev/skills/byx-darwin/gitflow-cli/gf-label-milestone"><img src="https://agentmods.dev/badge/skills/byx-darwin/gitflow-cli/gf-label-milestone.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.00047 | $0.01225 |
| Opus 5 | $0.00023 | $0.00613 |
| Sonnet 5 | $0.00009 | $0.00245 |
| Haiku 4.5 | $0.00005 | $0.00122 |
Grade A, and why
gf-label-milestone 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gf-label-milestone — Label & Milestone CRUD
Encapsulates CRUD operations for gf label and milestone command families.
Detailed parameters: docs/references/gf-label-milestone-params.md
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
Unified CRUD router for Labels (4 ops) and Milestones (5 ops).
Trigger Keywords
CN 创建标签 标签颜色 编辑里程碑 关闭里程碑 版本规划 删除标签
EN manage labels milestone CRUD label color due date close reopen
CLI gf label|milestone <subcommand>
When NOT to Use
| Scenario | Why Not | Use Instead |
|---|---|---|
| Assigning labels to Issues | This skill manages label/milestone definitions, not Issue labels | /gf-issue-triage for batch Issue labeling |
| Analyzing label distribution | This skill creates/edits/deletes labels, not analyzes usage | /gf-label-stats for read-only label analytics |
| Bulk closing or listing Issues | This skill manages labels and milestones only | /gf-issue for Issue CRUD operations |
| Automated release versioning | This skill manages milestone metadata, not release creation | /gf-release-helper for SemVer-based release automation |
| Batch deleting labels | This skill requires explicit confirmation per deletion and avoids destructive batch ops | Manual scripting with platform CLI |
CRUD Matrix
flowchart TD
U[User resource management] --> RES{Resource type?}
RES -->|Label| L_OP[Operation]
RES -->|Milestone| M_OP[Operation]
L_OP --> L_C[create]
L_OP --> L_L[list]
L_OP --> L_E[edit]
L_OP --> L_D[delete]
M_OP --> M_C[create]
M_OP --> M_L[list]
M_OP --> M_E[edit]
M_OP --> M_CL[close]
M_OP --> M_RO[reopen]
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 · 138 lines · 47 tokens per session scan A 6df5562f4f19
gf-label-milestone is a skill published in the GitHub repository byx-darwin/gitflow-cli (2 stars, last pushed today), licensed MIT. It adds 47 tokens to every session and 1,225 once invoked, about $0.0002 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…