Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add sgaunet/claude-plugins/plugin install software-engineeringWrote 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-w)<a href="https://agentmods.dev/skills/sgaunet/claude-plugins/feature-flow-w"><img src="https://agentmods.dev/badge/skills/sgaunet/claude-plugins/feature-flow-w/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-w"><img src="https://agentmods.dev/badge/skills/sgaunet/claude-plugins/feature-flow-w.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.00030 | $0.05756 |
| Opus 5.5 | $0.00012 | $0.02302 |
| Sonnet 5.5 | $0.00006 | $0.01151 |
| Haiku 4.5 | $0.00003 | $0.00576 |
Grade A, and why
feature-flow-w 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 22d 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 — 434 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Flow Worktree
Orchestrate a complete git workflow using worktrees for feature development. Creates a parallel working directory instead of switching branches, keeping your current branch untouched. Two modes:
- Staged Changes Mode (default): Analyze staged changes → worktree + branch → create issue → commit (in worktree)
- Issue Mode (
#<number>): Retrieve issue → validate relevance → worktree + branch → implement → lint → test → verify → commit → merge (all in worktree)
Use feature-flow-w instead of feature-flow when you want to work on multiple features simultaneously without leaving your current branch.
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-w #42, /feature-flow-w 42 --squash
Staged Mode examples: /feature-flow-w, /feature-flow-w add user auth, /feature-flow-w --skip-issue
Worktree Path Computation
Before creating any worktree, compute the target path:
- If
--worktree-path <path>(or-w <path>) provided → use that path (resolve to absolute if relative) - Default:
<repo-parent>/<repo-name>-<sanitized-branch>where/in branch name becomes-- Example: repo at
/home/user/my-project, branchfeat/add-auth→/home/user/my-project-feat-add-auth
- Example: repo at
- Validate directory does not already exist
Store <worktree-path> and <original-path> (result of pwd) for use throughout all phases.
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)
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.
- 22d ago First seen · 434 lines · 30 tokens per session scan A 6201fadc11ae
feature-flow-w is a skill published in the GitHub repository sgaunet/claude-plugins (16 stars, last pushed 8d ago), licensed MIT. It adds 30 tokens to every session and 5,756 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.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
retro
Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.
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.
review-resume
Comprehensive PM resume review and tailoring against 10 best practices including XYZ+S formula, keyword optimization, job-specific tailoring, and structure. Use when reviewing a PM resume, preparing for job applications, or improving resume impact.
identify-assumptions-new
Identify risky assumptions for a new product idea across 8 risk categories including Go-to-Market, Strategy, and Team. Use when evaluating startup risks, assessing a new product concept, or mapping assumptions for a new venture.