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-precommitnpx skills add byx-darwin/gitflow-cli --skill gf-precommitgit 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.00067 | $0.01120 |
| Opus 5 | $0.00034 | $0.00560 |
| Sonnet 5 | $0.00013 | $0.00224 |
| Haiku 4.5 | $0.00007 | $0.00112 |
Grade A, and why
gf-precommit 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 yesterday.
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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gf-precommit — Language-Agnostic Pre-commit Checks
Run language-appropriate fmt/lint/test before commit. Report results. Optionally configure Git hook.
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 NOT to Use
| Scenario | Why Not | Use Instead |
|---|---|---|
| Running full 6-gate quality verification | This skill runs 3 checks (fmt/lint/test), not the full quality pipeline | /gf-quality for build + test + coverage + format + static + pre-commit |
| Analyzing remote CI/CD pipeline health | This skill runs local checks, not remote pipeline analysis | /gf-pipeline-analyzer for CI/CD success-rate and failure analysis |
| Auto-fixing all lint and format issues | This skill reports issues and requires confirmation before any fix | Show diff first, then fix with explicit user approval |
| Running security-specific audits | This skill runs general quality checks, not security scans | /gf-security-check for cargo audit, cargo deny, secret detection |
| Configuring hooks without user consent | Hook configuration is a side effect requiring authorization | Ask user first before installing or modifying hooks |
| Inspecting existing commits | This skill runs checks before commit, not on already-pushed commits | /gf-commit for viewing/diffing existing commits |
Step 1: Language Detection
Same as gf-quality. Check marker files in project root:
| Marker | Language | Reference |
|---|---|---|
Cargo.toml |
Rust | references/rust.md |
go.mod |
Go | references/go.md |
pom.xml / build.gradle |
Java | references/java.md |
pyproject.toml / setup.py |
Python | references/python.md |
package.json |
Node.js | references/node.md |
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 114 lines · 67 tokens per session scan A b42c26724f28
gf-precommit is a skill published in the GitHub repository byx-darwin/gitflow-cli (2 stars, last pushed yesterday), licensed MIT. It adds 67 tokens to every session and 1,120 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.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…