A first-time setup helper for vibe-flow, a workflow that tracks coding work through vibe-kanban. It chooses a vibe-kanban project and creates the small configuration and local state files the repository needs.

Use it when starting vibe-flow in a new Git repository or when changing its project settings.

It removes the manual work of finding a project ID, copying configuration, creating folders, and updating .gitignore. Re-running it is safe and can be used to reconfigure the project.

vibe-init — Skill for Claude Code by OAI-Labs

Install

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.

Any agent

npx skills add OAI-Labs/vibe-flow --skill vibe-init

Clone the repo

git clone --depth 1 https://github.com/OAI-Labs/vibe-flow

Made for: Claude Code.

Or install vibe-flow, the plugin that ships this one along with the rest of its 14 skills, 2 agents.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/oai-labs/vibe-flow/vibe-init/github.svg)](https://agentmods.dev/skills/oai-labs/vibe-flow/vibe-init)

Your own site

<a href="https://agentmods.dev/skills/oai-labs/vibe-flow/vibe-init"><img src="https://agentmods.dev/badge/skills/oai-labs/vibe-flow/vibe-init/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/oai-labs/vibe-flow/vibe-init"><img src="https://agentmods.dev/badge/skills/oai-labs/vibe-flow/vibe-init.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,501 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00056	$0.01501
Opus 5	$0.00028	$0.00750
Sonnet 5	$0.00011	$0.00300
Haiku 4.5	$0.00006	$0.00150

Measured 9d ago against content hash cf7dc318823a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

vibe-init 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 9d 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.

plugins/vibe-flow/skills/vibe-init/SKILL.md · 174 lines

How it starts

The opening of the file, as written. The whole thing — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.

vibe-init

Overview

One-shot setup for a repo that will use vibe-flow. Replaces the manual "copy .vibe-flow.example.yaml, hunt for project_id, create state dir" dance. Asks only what's needed — nothing else.

Core principle: One required answer (which project). Everything else has defaults.

Announce at start: "I'm using the vibe-init skill to set up vibe-flow for this repo."

When to use

User says "set up vibe-flow", "init vibe-flow", or runs /vibe-flow:vibe-init
First time using vibe-flow in a repo (no .vibe-flow.yaml present)
User wants to reconfigure (re-run to re-pick project / edit defaults)

Do NOT use if:

.vibe-flow.yaml already exists AND user hasn't asked to reconfigure — skip with a note
Not inside a git repo — bail and ask user to git init first
vibe-kanban MCP not connected — bail and point at README "MCP setup"

The process

Step 1: Preflight

# Must be in a git repo
git rev-parse --show-toplevel

Verify MCP:

Call list_organizations. If it errors → stop, tell user MCP isn't reachable, point to README.

Check idempotency:

If .vibe-flow.yaml exists → ASK: "Config already present. Reconfigure, show current, or cancel?"
If cancel → exit cleanly.

Step 2: Ask the minimum

Q1 (required): Project. Call list_projects. Show a numbered list of name — project_id. User picks one.

Do NOT ask the user to paste an ID. Always offer selection.

Q2 (optional, one prompt): Concurrency + budget. Offer defaults inline; accept Enter to keep them:

max_parallel [5]:
cost_budget_usd [50]:
wave_barrier [merge / pr-open] (default: merge):

Q3 (optional): Notifications.

Slack webhook (Enter to skip):
Discord webhook (Enter to skip):

Q4 (optional): ready_to_merge column.

vibe-kanban ships with todo / in_progress / in_review / done by default but projects can add custom columns. MCP does NOT expose a way to create columns — if the user wants this one, they must add it themselves in vibe-kanban UI → Project Settings → Statuses first.

Read the full file on GitHub · 174 lines

Changes

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.

9d ago First seen · 174 lines · 56 tokens per session scan A cf7dc318823a

Subscribe to this mod's changes

vibe-init is a skill published in the GitHub repository OAI-Labs/vibe-flow (1 stars, last pushed 1mo ago), licensed MIT. It adds 56 tokens to every session and 1,501 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.

Claude Code agent-orchestration ai-agents claude-code-plugin claude-plugin

vibe-init

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

vibe-init

Overview

When to use

The process

Step 1: Preflight

Step 2: Ask the minimum

What this file has done since we first saw it

Other skills, from other repositories

implement

loop-on-ci

run-smoke-tests

browser-use

tdd

to-tickets