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 dbinky/dbinky-skill-set/plugin install pr-reviewWrote 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/dbinky/dbinky-skill-set/feature-pipeline)<a href="https://agentmods.dev/skills/dbinky/dbinky-skill-set/feature-pipeline"><img src="https://agentmods.dev/badge/skills/dbinky/dbinky-skill-set/feature-pipeline.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.1 | $0.00032 | $0.00285 |
| Opus 5 | $0.00016 | $0.00143 |
| Sonnet 5 | $0.00006 | $0.00057 |
| Haiku 4.5 | $0.00003 | $0.00028 |
Grade A, and why
feature-pipeline 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 8d 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.
What it actually says
Feature Pipeline
Orchestrate the complete feature development pipeline from brainstorming through PR review. Steps 1-2 are interactive (user present for Q&A), steps 3-9 are fully automated (user walks away).
Usage
/feature-pipeline {description of the product feature}
/feature-pipeline {description} --slug user-auth
/feature-pipeline {description} --spec-only
/feature-pipeline {description} --max-iterations 300 --priority normal
Process
Read and follow the orchestrator instructions exactly:
Orchestrator file: agents/feature-pipeline-orchestrator.md (relative to this plugin's root)
The orchestrator will:
- Parse arguments and initialize paths
- Guide interactive spec brainstorming (user present)
- Guide interactive design brainstorming (user present)
- Dispatch automated steps as isolated subagents — alignment, planning, second alignment, implementation, ralph planning, ralph submission
- Notify Teams at key milestones
- Report final status
IMPORTANT: Read the orchestrator file using the path ${CLAUDE_PLUGIN_ROOT}/agents/feature-pipeline-orchestrator.md and follow it exactly.
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.
- 8d ago First seen · 34 lines · 32 tokens per session scan A 39be694c3cd0
feature-pipeline is a skill published in the GitHub repository dbinky/dbinky-skill-set (5 stars, last pushed 2mo ago), licensed MIT. It adds 32 tokens to every session and 285 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
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…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…