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.
/plugin marketplace add swt-labs/vibe-better-with-claude-code-vbw/plugin install vbwWrote 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/skills/swt-labs/vibe-better-with-claude-code-vbw/profile)<a href="https://agentmods.dev/skills/swt-labs/vibe-better-with-claude-code-vbw/profile"><img src="https://agentmods.dev/badge/skills/swt-labs/vibe-better-with-claude-code-vbw/profile/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/skills/swt-labs/vibe-better-with-claude-code-vbw/profile"><img src="https://agentmods.dev/badge/skills/swt-labs/vibe-better-with-claude-code-vbw/profile.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.00057 | $0.00529 |
| Opus 5.5 | $0.00023 | $0.00212 |
| Sonnet 5.5 | $0.00011 | $0.00106 |
| Haiku 4.5 | $0.00006 | $0.00053 |
Grade A, and why
profile 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.
What it actually says
Write to the user's level, explanation depth and involvement.
"${CLAUDE_PLUGIN_ROOT}/bin/vbw" config 2>&1 || true
"${CLAUDE_PLUGIN_ROOT}/bin/vbw" interview 2>&1 || true
The user said: $ARGUMENTS
Output above says not a VBW project: set up first (vbw init and vbw statusline on, one line saying so), then run vbw config again.
Presets (each sets two things with vbw config set):
| Preset | profile (models) |
autonomy |
Good for |
|---|---|---|---|
| Careful | quality (Opus for the Architect, Lead, Dev and Debugger) |
guided: explains each step and waits for "go" |
learning, a first project, risky changes |
| Standard | balanced (Opus for the Architect and the Lead, Sonnet for the rest) |
balanced: keeps going, stops for your decisions, approval, checking and shipping |
most work (the default) |
| Fast | budget (Haiku for Scout, Sonnet for the rest, QA included) |
hands-off: takes its own recommendations on decisions and lists them for you |
small changes, once you trust it |
Preset named: apply it, show the result. Else show current settings and ask (AskUserQuestion) which preset, best fit first, or "My own mix" (then ask the two settings separately). Approval, checking and shipping always stop for the user.
Interview answers above (vbw interview) set how VBW talks to the user. Show them in plain words. To change one answer: ask which and its new value (AskUserQuestion; a wrong value's error lists allowed ones), change only that one answer:
vbw interview set level VALUEvbw interview set depth VALUEvbw interview set involvement VALUE
Interview not done: say so, point to /vbw:vibe, which asks it.
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 · 36 lines · 57 tokens per session scan A 96c6230d6088
profile 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 57 tokens to every session and 529 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.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…