vibe

vibe is a skill for Claude Code from swt-labs/vibe-better-with-claude-code-vbw. It costs 40 tokens per session (3,225 once invoked), scanned A, original, MIT.

A guided workflow for VBW projects, moving work through steps such as defining requirements, planning, building, checking, fixing, accepting, and shipping.

In plain words
What is it for?
Use it to manage development work from an initial request through delivery and acceptance.
Why use it?
It gives each request a defined next step and requires approval and a build before project files change.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the vbw plugin — 34 skills, 7 agents, 4 hooks shipped together

Good fit Use it to manage development work from an initial request through delivery and acceptance.

Compare 6 skills from other repositories ↓
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.

agentmods badge for vibe

README.md
[![agentmods](https://agentmods.dev/badge/skills/swt-labs/vibe-better-with-claude-code-vbw/vibe/github.svg)](https://agentmods.dev/skills/swt-labs/vibe-better-with-claude-code-vbw/vibe)
Your own site
<a href="https://agentmods.dev/skills/swt-labs/vibe-better-with-claude-code-vbw/vibe"><img src="https://agentmods.dev/badge/skills/swt-labs/vibe-better-with-claude-code-vbw/vibe/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

Your own site · 80×15
<a href="https://agentmods.dev/skills/swt-labs/vibe-better-with-claude-code-vbw/vibe"><img src="https://agentmods.dev/badge/skills/swt-labs/vibe-better-with-claude-code-vbw/vibe.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,225 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.00040 $0.03225
Opus 5.5 $0.00016 $0.01290
Sonnet 5.5 $0.00008 $0.00645
Haiku 4.5 $0.00004 $0.00323

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

Security

Grade A, and why

vibe 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/vibe/SKILL.md · 157 lines

How it starts

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

VBW

Kernel decides next step; you carry it out. Even for a one-line fix: no project file changes until the contract is approved and a build runs.

"${CLAUDE_PLUGIN_ROOT}/bin/vbw" next --json 2>&1 || true
"${CLAUDE_PLUGIN_ROOT}/bin/vbw" config models 2>&1 || true
"${CLAUDE_PLUGIN_ROOT}/bin/vbw" workflows on 2>&1 || true
"${CLAUDE_PLUGIN_ROOT}/bin/vbw" config autonomy 2>&1 || true

User said: $ARGUMENTS

Every new request, now or later, goes to vbw:triage first; "what's next" or "suggest next" follows vbw:whats-next.

No JSON above (skill shell execution off): run VBW_SESSION_ID=${CLAUDE_SESSION_ID} vbw next --json, vbw config models, vbw config autonomy with Bash first. "not a VBW project": set it up yourself (vbw init, vbw statusline on; say what was set up in one line), then VBW_SESSION_ID=${CLAUDE_SESSION_ID} vbw next --json again.

Setting stated in words

Before any step, read the user's words (now, or later in the session). Words naming guided, balanced or hands-off, or a plain phrase clearly meaning one ("ask me before each step" = guided, "do not ask, just go" = hands-off), run vbw config set autonomy <value> first. Say in one line what was set, then follow the Autonomy section with that value, not the line loaded above.

  • Same as the current setting: it writes nothing and says nothing about it.
  • Words that do not clearly name one setting change nothing: never guess.
  • Stated later in the session: record it at once; it applies from the next step. A switch to guided while the autonomous run is armed runs vbw auto off ${CLAUDE_SESSION_ID}; a switch to balanced or hands-off runs vbw auto on ${CLAUDE_SESSION_ID} once.
  • --auto runs alone this time only and never changes the setting.

Autonomy

Last line above, or the value just set, = how much VBW does alone. Approval, accept and shipping always stop for user.

  • balanced, hands-off: run vbw auto on ${CLAUDE_SESSION_ID} once; VBW keeps going until a step needs user.
  • hands-off: at needs_decisions, take the recommended option (as decide and tell me below).
  • guided: before each step not needing user, say what and why, ask (AskUserQuestion): "Go ahead", "Explain more", "Stop here". --auto runs alone this time.

Read the full file on GitHub · 157 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. today First seen · 157 lines · 40 tokens per session scan A 702c151e0958

Subscribe to this mod's changes

vibe 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 40 tokens to every session and 3,225 once invoked, about $0.0002 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.

Related

Other skills, from other repositories