vibe-import-kanban

vibe-import-kanban is a skill for Claude Code from OAI-Labs/vibe-flow. It costs 65 tokens per session (1,303 once invoked), scanned A, original, MIT.

A one-time importer that copies existing vibe-kanban issues into a local plan file for vibe-ship-fast, a workflow that delivers them through one final pull request. It preserves the IDs needed to report the results back later, without changing the kanban board.

In plain words
What is it for?
Use it when issues already exist in vibe-kanban and you want to process them locally, then export their completed status after the final pull request is merged.
Why use it?
It lets a local run work from an existing kanban board while making clear that the copied plan can become outdated. You can re-import if the board changes during the run.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

Part of the vibe-flow plugin — 14 skills, 2 agents shipped together

Good fit Use it when issues already exist in vibe-kanban and you want to process them locally, then export their completed status after the final pull request is merged.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/oai-labs/vibe-flow/vibe-import-kanban
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-import-kanban
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.

agentmods badge for vibe-import-kanban

README.md
[![agentmods](https://agentmods.dev/badge/skills/oai-labs/vibe-flow/vibe-import-kanban/github.svg)](https://agentmods.dev/skills/oai-labs/vibe-flow/vibe-import-kanban)
Your own site
<a href="https://agentmods.dev/skills/oai-labs/vibe-flow/vibe-import-kanban"><img src="https://agentmods.dev/badge/skills/oai-labs/vibe-flow/vibe-import-kanban/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.

agentmods 80×15 button for vibe-import-kanban

Your own site · 80×15
<a href="https://agentmods.dev/skills/oai-labs/vibe-flow/vibe-import-kanban"><img src="https://agentmods.dev/badge/skills/oai-labs/vibe-flow/vibe-import-kanban.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 65 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,303 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00065 $0.01303
Opus 5 $0.00032 $0.00651
Sonnet 5 $0.00013 $0.00261
Haiku 4.5 $0.00006 $0.00130

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

Security

Grade A, and why

vibe-import-kanban 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 11d 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-import-kanban/SKILL.md · 123 lines

How it starts

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

vibe-import-kanban

Overview

One-way snapshot from vibe-kanban to a local plan file. Does not modify kanban state. The resulting plan-local.json is the input for vibe-ship-fast; the preserved kanban_id / simple_id per issue let vibe-export-kanban post the merge result back to the right issue after the final PR lands.

Core principle: Snapshot, don't subscribe. No polling, no two-way sync, no live updates. If kanban changes mid-flight, the local plan is stale by design — re-import if you need to.

Announce at start: "I'm using the vibe-import-kanban skill to snapshot issues."

When to use

  • Issues already exist in vibe-kanban (created by you, a teammate, or vibe-plan without --local)
  • You want vibe-ship-fast's local workflow (one PR at the end) but still want the kanban board to reflect "done" later
  • Solo run on a shared project

Do NOT use if:

  • Issues don't exist yet → vibe-plan --local (skip kanban entirely)
  • You want per-issue PRs and per-PR review on GitHub → vibe-ship (no import needed)
  • A .vibe-flow/plan-local.json from this run already exists → either resume vibe-ship-fast or delete the file first

The process

Step 1: Resolve scope

Read .vibe-flow.yaml for project_id. If $ARGUMENTS overrides, use that.

Ask the user (or take from $ARGUMENTS) which subset:

  • All open issues in the project
  • Issues with a specific tag (e.g., sprint:q2)
  • A parent issue's sub-tree
  • Explicit list of simple_ids

Step 2: Pull from kanban

Use MCP:

  1. list_issues(project_id, status_filter, tag_filter) for the candidate set
  2. For each candidate: get_issue(issue_id) for the full description and tags
  3. list_issue_relationships(issue_id) to capture blocks / blocked_by edges

Do NOT issue any write call. This skill is read-only against kanban.

Step 3: Map to local schema

For each kanban issue, build:

{
  "id": "L<n>",
  "title": "<kanban title>",
  "description": "<kanban description, verbatim>",
  "tier": "<read from tag tier:t0..t4, fallback T2>",
  "depends_on": ["L<m>", "..."],
  "tags": ["<kanban tags except tier:* and the internal vibe-flow ones>"],
  "brainstorm": "<from tag brainstorm:interactive|autonomous, else null>",
  "files_hint": [],
  "kanban_id": "<issue_id>",
  "simple_id": "<simple_id>"
}

Read the full file on GitHub · 123 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.

  1. 11d ago First seen · 123 lines · 65 tokens per session scan A f1974271f46d

Subscribe to this mod's changes

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

Related

Other skills, from other repositories

lead

Use when acting as the factory tech lead: classify work, ask the minimum questions, create tickets, and dispatch without implementing.

Kripu77/software-factory · 27 tokens

to-tickets

Use when breaking a plan into tracer-bullet GitHub issues with blocking edges.

Kripu77/software-factory · 20 tokens

merge-review

Reviews pending fleet worktree merges before they're accepted. Reads the merge-check queue, detects file-level conflicts between branches, proposes a safe merge order, and surfaces reconciliation plans for overlapping changes.

SethGammon/Citadel · 40 tokens

workspace

Multi-repo campaign coordinator. Same lifecycle as fleet -- scope claims, discovery relay, wave-based execution -- but the unit of work is a repo, not a file. Coordinates campaigns across repositories with shared context.

SethGammon/Citadel · 44 tokens

decision-map

Turn a loose idea into a git-tracked, session-resumable map of typed investigation tickets, then drive them to resolution one at a time. The planning-loop engine for work that is still being figured out — too fuzzy for a campaign, too big for a single intake item. Resolved tickets graduate into .planning/intake/ for…

SethGammon/Citadel · 77 tokens

unharness

Safely leave Citadel using the active adoption receipt. Produces a no-write, reviewable plan, preserves a portable archive, removes only exact owned material, and reports modified or externally registered surfaces as retained or unknown. Legacy installs must be imported before exact leave is claimed.

SethGammon/Citadel · 59 tokens