A conversion command for moving a VBW 1 project into VBW 2 through a short question-and-answer process. It leaves the old planning folder unchanged unless you explicitly remove it.

Use it to review an older VBW project, bring its unfinished work into the newer format, and decide whether the old folder should later be removed.

It preserves the older project files while carrying forward the work and decisions you still want to use.

convert — Skill for Claude Code by swt-labs

Install

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.

Claude Code

/plugin marketplace add swt-labs/vibe-better-with-claude-code-vbw

Claude Code

/plugin install vbw

Made for: Claude Code.

Or install vbw, the plugin that ships this one along with the rest of its 34 skills, 7 agents, 4 hooks.

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/swt-labs/vibe-better-with-claude-code-vbw/convert/github.svg)](https://agentmods.dev/skills/swt-labs/vibe-better-with-claude-code-vbw/convert)

Your own site

<a href="https://agentmods.dev/skills/swt-labs/vibe-better-with-claude-code-vbw/convert"><img src="https://agentmods.dev/badge/skills/swt-labs/vibe-better-with-claude-code-vbw/convert/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/swt-labs/vibe-better-with-claude-code-vbw/convert"><img src="https://agentmods.dev/badge/skills/swt-labs/vibe-better-with-claude-code-vbw/convert.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 694 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.00037	$0.00694
Opus 5.5	$0.00015	$0.00278
Sonnet 5.5	$0.00007	$0.00139
Haiku 4.5	$0.00004	$0.00069

Measured today against content hash 607da6ad6886, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

convert 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 today.

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.

plugin/skills/convert/SKILL.md · 32 lines

What it actually says

"${CLAUDE_PLUGIN_ROOT}/bin/vbw" legacy 2>&1 || true
"${CLAUDE_PLUGIN_ROOT}/bin/vbw" legacy review 2>&1 || true
"${CLAUDE_PLUGIN_ROOT}/bin/vbw" status 2>&1 || true
"${CLAUDE_PLUGIN_ROOT}/bin/vbw" interview 2>&1 || true

Write to user's level, explanation depth and involvement (above; "-": plain words).

Facts above describe the VBW 1 plan. "legacy": false: nothing to convert; say so, stop. "converted": true: already converted; say so, offer only the removal question (step 6).

The review above (vbw legacy review: finished, last used, match with the code, half done, recommendation) can be shown on demand when the user asks; same plain words as the interview step.

Carry over what the user still wants, through their answers. Never change .vbw-planning/; only vbw legacy remove may, only on their word.

Set up. Status above says not a VBW project: run vbw init.
Read only files in files (project, requirements, roadmap, state, shipped notes). Tell user in a few lines what the project is, what finished (phases marked done, shipped milestones), what was open.
Ask one question at a time (AskUserQuestion), recommendation first, what you found in the question or preview:
- Goals: still what the project is for? Write agreed goals under ## Goals in .vbw/spec.md.
- What to do next: which open requirements and unfinished phases belong in the first VBW 2 milestone? Recommend must-haves and work already started; rest waits in backlog. Each kept: restate as something a user can observe; say whether a test can prove it (auto) or only they can judge (human). Add with vbw spec add auto|human "statement"; park the rest with vbw todo add.
- Ideas and decisions: after checking they still hold, carry over open todos (vbw todo add) and decisions (vbw decide "decision" "why").
History. Under ## History (VBW 1) in .vbw/spec.md (not in Requirements), one line per finished milestone or phase. Name the milestone: vbw milestone rename "<title>".
Record it: vbw legacy done.
Ask: "Delete the old .vbw-planning/ folder, or keep it?" Recommend keeping. git.tracked above 0: its files stay in git history either way; 0: deleting is permanent. Delete only on their answer: vbw legacy remove.
Continue with the vbw:vibe skill: VBW maps the code if needed, plans the new milestone, asks for approval.

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.

today First seen · 32 lines · 37 tokens per session scan A 607da6ad6886

Subscribe to this mod's changes

convert is a skill published in the GitHub repository swt-labs/vibe-better-with-claude-code-vbw (85 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 694 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-10-22.

Project management

story-readiness

Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.

Donchitos/Claude-Code-Game-Studios · 48 tokens

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

projects

List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.

me2resh/apexyard · 24 tokens

qa-project-bootstrap

Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…

petrkindlmann/qa-skills · 124 tokens