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/vibe)<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.
<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>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.00040 | $0.03225 |
| Opus 5.5 | $0.00016 | $0.01290 |
| Sonnet 5.5 | $0.00008 | $0.00645 |
| Haiku 4.5 | $0.00004 | $0.00323 |
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.
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 runsvbw auto on ${CLAUDE_SESSION_ID}once. --autoruns 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 (asdecide and tell mebelow). - guided: before each step not needing user, say what and why, ask
(AskUserQuestion): "Go ahead", "Explain more", "Stop here".
--autoruns alone this time.
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 · 157 lines · 40 tokens per session scan A 702c151e0958
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.
Other skills, from other repositories
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.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
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…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
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,"…