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-regressionnpx skills add byx-darwin/gitflow-cli --skill gf-regressiongit 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.00060 | $0.02885 |
| Opus 5 | $0.00030 | $0.01443 |
| Sonnet 5 | $0.00012 | $0.00577 |
| Haiku 4.5 | $0.00006 | $0.00288 |
Grade A, and why
gf-regression 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 — 354 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gf-regression
Runs scripts/smoke-test.sh, parses PASS/FAIL/SKIP, delegates real failures to /gf-autoreport-bug. Defaults to --read-only. Does not fix bugs, edit scripts, or modify remotes.
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
Use this skill when you need to verify that the gf CLI is working correctly
after changes, before release, or when debugging CLI-related issues.
Specific Scenarios
| # | Scenario | Trigger Phrase | Expected Action |
|---|---|---|---|
| 1 | Post-change verification | "verify my changes didn't break gf" | Run read-only smoke test, report PASS/FAIL |
| 2 | Pre-release gate | "run pre-release checks" | Run smoke test as part of release preparation |
| 3 | Debugging CLI issues | "gf commands are failing" | Run smoke test to identify which operations fail |
| 4 | Quick health check | "is gf working?" | Run minimal smoke test, report status |
| 5 | Regression detection | "check for regressions" | Run full smoke test, compare with baseline |
Language-Specific Triggers
| English | 中文 | Context |
|---|---|---|
| smoke test | 冒烟测试 | Quick CLI health check |
| regression test | 回归测试 | Post-change verification |
| pre-release check | 发版前检查 | Before publishing release |
| verify CLI | 验证 CLI | Confirm CLI functionality |
| gf is broken | gf 坏了 | Debug CLI failures |
When NOT to Use
Do NOT use this skill in the following scenarios:
| Scenario | Why Not | Use Instead |
|---|---|---|
| Fixing a bug | This skill only detects and reports bugs, doesn't fix them | /gf-workflow for bug fixes |
| Code review | This skill runs tests, doesn't review code | /gf-pr-review for code review |
| Full quality gate | This skill only runs smoke tests, not full CI | /gf-quality for complete quality checks |
| Testing other projects | This skill is designed for gf CLI only |
Use project-specific test commands |
| CI pipeline | Smoke tests with autoreport shouldn't run in CI | Use scripts/smoke-test.sh directly with exit code |
| Performance testing | This skill checks functionality, not performance | Use benchmarking tools |
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 · 354 lines · 60 tokens per session scan A 7d5b5fde5f67
gf-regression is a skill published in the GitHub repository byx-darwin/gitflow-cli (2 stars, last pushed 2d ago), licensed MIT. It adds 60 tokens to every session and 2,885 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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.