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/discuss)<a href="https://agentmods.dev/skills/swt-labs/vibe-better-with-claude-code-vbw/discuss"><img src="https://agentmods.dev/badge/skills/swt-labs/vibe-better-with-claude-code-vbw/discuss/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/discuss"><img src="https://agentmods.dev/badge/skills/swt-labs/vibe-better-with-claude-code-vbw/discuss.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.00035 | $0.00454 |
| Opus 5.5 | $0.00014 | $0.00182 |
| Sonnet 5.5 | $0.00007 | $0.00091 |
| Haiku 4.5 | $0.00003 | $0.00045 |
Grade A, and why
discuss 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
"${CLAUDE_PLUGIN_ROOT}/bin/vbw" status 2>&1 || true
"${CLAUDE_PLUGIN_ROOT}/bin/vbw" show decisions 2>&1 || true
"${CLAUDE_PLUGIN_ROOT}/bin/vbw" interview 2>&1 || true
Write to the user's level, explanation depth and involvement (above; "-": plain words).
The user wants to think this through: $ARGUMENTS
If that is empty, ask what is on their mind, offering starting points that fit the project's state.
Help them decide well, not for them. Bring up what they haven't considered when it matters: cost, where data lives, security, maintenance effort, what is hard to change later.
- Understand first: read what you need (
.vbw/spec.md,.vbw/map.md, the code) and say back in a sentence what you understood. - Ask one question at a time (AskUserQuestion): recommendation first, marked "(Recommended)", a trade-off per option. Ask only what changes the outcome.
- Record the outcome, and say what you recorded:
- each decision:
vbw decide "<what was decided>" "<why>"; - a new or changed requirement:
vbw spec add auto|human "<statement>", or edit.vbw/spec.mdand runvbw spec sync; say that the plan's contract will need approval again; - an idea for later:
vbw todo add "<idea>".
- each decision:
- Close with what was decided;
/vbw:vibecontinues from it.
Outside a VBW project (the status above says so), discuss all the same, and
offer /vbw:init at the end so the decisions can be kept.
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 · 40 lines · 0 tokens per session scan A 2f7f584daf0a
discuss 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 35 tokens to every session and 454 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.
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,"…