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 skills add sgaunet/claude-plugins --skill feature-flowgit clone --depth 1 https://github.com/sgaunet/claude-pluginsWrote 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/sgaunet/claude-plugins/feature-flow)<a href="https://agentmods.dev/skills/sgaunet/claude-plugins/feature-flow"><img src="https://agentmods.dev/badge/skills/sgaunet/claude-plugins/feature-flow/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/sgaunet/claude-plugins/feature-flow"><img src="https://agentmods.dev/badge/skills/sgaunet/claude-plugins/feature-flow.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00024 | $0.04278 |
| Opus 5.5 | $0.00010 | $0.01711 |
| Sonnet 5.5 | $0.00005 | $0.00856 |
| Haiku 4.5 | $0.00002 | $0.00428 |
Grade A, and why
feature-flow 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 21d 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 — 349 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Flow
Orchestrate a complete git workflow for feature development. Two modes:
- Staged Changes Mode (default): Analyze staged changes → branch → create issue → commit
- Issue Mode (
#<number>): Retrieve issue → validate relevance → branch → implement → lint → test → verify → commit → merge
Automates repetitive workflow setup (branching, issues, commits, quality checks, merge requests).
Mode Detection
Route based on $argument: first positional argument matching #<number> or bare <number> → Issue Mode; otherwise → Staged Changes Mode.
Issue Mode examples: /feature-flow #42, /feature-flow 42 --squash
Staged Mode examples: /feature-flow, /feature-flow add user auth, /feature-flow --skip-issue
Staged Changes Mode (5 Phases)
Phase 1: Discovery & Validation (Automatic)
Execute parallel git commands: git status and git diff --staged
Detect Repository Host: Use the detect-repo-host skill to identify the hosting service (GitHub, GitLab, or Forgejo) and extract owner/repo details.
Analysis steps:
-
Analyze staged changes:
- Extract file paths, extensions, and types
- Determine change type: new files →
feat, test+fixes →fix, docs only →docs, structural →refactor, build/config →chore - Extract primary scope from directory (e.g.,
src/api/→api,internal/auth/→auth)
-
Generate proposed branch name:
- Format:
<type>/<scope>-<description>(kebab-case, 2-4 words) - Types: feat, fix, refactor, docs, chore, test, perf, ci
- Examples:
feat/api-user-profile,fix/auth-jwt-validation,docs/readme-update
- Format:
Error handling:
- No staged changes → Abort: "No staged changes found. Stage files with 'git add' first."
- Repository host detection fails → The
detect-repo-hostskill provides detailed error messages
Phase 2: Branch Creation (User Confirmation)
Parse flags: --skip-branch or -b → skip this phase.
If not skipped:
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.
- 21d ago First seen · 349 lines · 24 tokens per session scan A 0bed10994eb8
feature-flow is a skill published in the GitHub repository sgaunet/claude-plugins (16 stars, last pushed 7d ago), licensed MIT. It adds 24 tokens to every session and 4,278 once invoked, about $0.0001 per session on Opus 5.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-09-25.
Other skills, from other repositories
glab
Expert guidance for using the GitLab CLI (glab) to manage GitLab issues, merge requests, CI/CD pipelines, repositories, and other GitLab operations from the command line. Use this skill when the user needs to interact with GitLab resources or perform GitLab workflows.
commit-message
Use ANY time the user signals they want to commit staged changes — including bare "commit", "/commit", "commit this", "commit these changes", "let's commit", "make a commit", "git commit", "write a commit message", "make a conventional commit", "use conventional commits", or any equivalent phrasing in context (e.g.…
committing-staged-with-message
Generate commit message for staged changes, pause for approval, then commit. Stage files first with git add, then run this skill.
claim
Acquire, renew or release a Fakoli State task lease when beginning work or recovering an interrupted claim.
detecting-secrets
Detect hardcoded secrets, API keys, tokens, and credentials in code and git history. Use when auditing for leaked secrets or before publishing code.
sprint-plan
Plan a sprint with capacity estimation, story selection, dependency mapping, and risk identification. Use when preparing for sprint planning, estimating team capacity, selecting stories, or balancing sprint scope against velocity.