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.
git clone --depth 1 https://github.com/felvieira/claude-skills-fvWrote 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/commands/felvieira/claude-skills-fv/pipeline)<a href="https://agentmods.dev/commands/felvieira/claude-skills-fv/pipeline"><img src="https://agentmods.dev/badge/commands/felvieira/claude-skills-fv/pipeline/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/commands/felvieira/claude-skills-fv/pipeline"><img src="https://agentmods.dev/badge/commands/felvieira/claude-skills-fv/pipeline.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.00018 | $0.00473 |
| Opus 5 | $0.00009 | $0.00236 |
| Sonnet 5 | $0.00004 | $0.00095 |
| Haiku 4.5 | $0.00002 | $0.00047 |
Grade A, and why
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 12d 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
/pipeline — Pipeline Clássico
Objetivo: Executar o ciclo padrão de desenvolvimento de feature pequena/média: spec → plan → build → test → review → ship.
Skill ativada: 09 — Orchestrator (coordena todas as etapas)
Fluxo:
/spec— especificar com critérios de aceitação (markdown interno emdocs/specs/)/plan— classificar e montar pipeline mínimo. Se feature multi-camada: produz tabela de vertical slices.- Para cada slice (paralelo se independentes):
/build— DB + backend + frontend juntos no mesmo worktree/test— teste e2e cobrindo a feature ponta-a-ponta/review— review final + security do slice
/ship— release e deploy (após todos os slices mergeados)
Quando usar este (/pipeline clássico):
- feature pequena/média (<1 sprint)
- spec já clara, equipe conhece o terreno
- não precisa publicar PRD/issues no GitHub/Linear/Jira
- não precisa TDD enforced
Quando usar o variante /pipeline-discovery:
- feature grande/nova/ambígua, briefing vago, equipe nova com a área
- vai paralelizar com 2+ workers
- precisa publicar PRD + issues no issue tracker
- TDD obrigatório por slice
Diferenças /pipeline vs /pipeline-discovery: ver tabela em .claude/commands/pipeline-discovery.md.
Input esperado: Descrição completa da feature ou requisito (idealmente uma feature por vez; epic vira lista de slices).
Output esperado: Cada slice mergeado independentemente, demo-able. Feature completa quando todos os slices mergeados.
Policies relevantes:
policies/vertical-slices.md— obrigatória para feature multi-camada (impede plano layer-first)- Todas as policies do kit são aplicáveis conforme a etapa
policies/model-routing.md— modelo certo por fase
Uso: /pipeline [descrição da feature]
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.
- 12d ago First seen · 44 lines · 18 tokens per session scan A 40608d450eaa
pipeline is a command published in the GitHub repository felvieira/claude-skills-fv (23 stars, last pushed yesterday), licensed Apache-2.0. It adds 18 tokens to every session and 473 once invoked, about $0.0001 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-30.
Other commands, from other repositories
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
ship
Deploy feature through automated staging validation to production with rollback testing.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
ship
Ship is the operational release-prep flow for a connected project repo.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.
rally-merge-pr
You are merging the current branch's PR and syncing the feature branch with main. Follow each step exactly.