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/triage)<a href="https://agentmods.dev/skills/swt-labs/vibe-better-with-claude-code-vbw/triage"><img src="https://agentmods.dev/badge/skills/swt-labs/vibe-better-with-claude-code-vbw/triage/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/triage"><img src="https://agentmods.dev/badge/skills/swt-labs/vibe-better-with-claude-code-vbw/triage.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.00043 | $0.00791 |
| Opus 5.5 | $0.00017 | $0.00316 |
| Sonnet 5.5 | $0.00009 | $0.00158 |
| Haiku 4.5 | $0.00004 | $0.00079 |
Grade A, and why
triage 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Triage
"${CLAUDE_PLUGIN_ROOT}/bin/vbw" triage 2>&1 || true
"${CLAUDE_PLUGIN_ROOT}/bin/vbw" interview 2>&1 || true
Above: the active milestone, its requirements, the open backlog and the user's answers. Write to the user's level, explanation depth and involvement ("-": plain words).
Router calls this for each new idea, before any requirement, planning or file change. At every autonomy setting (guided, balanced, hands-off) the idea is sorted and the user confirms or overrules it.
When it applies
New idea: a feature, change, fix or wish not yet in the spec. Not a new idea, so no triage: an answer to a question VBW asked, "continue" or "go on", an approval, a question about the project, an autonomy setting stated in words (guided, balanced, hands-off, or a phrase that means one): the router records it; the rest of the same message goes to triage as usual.
Idea already matches a requirement or open backlog item: name it, no new entry. For a backlog item, offer to move it to now (vbw spec add, then vbw todo done).
The sorting menu
One line per idea, one line each, all inside one AskUserQuestion; the line is inside it, so the user decides from what the menu shows. Per idea, the question text holds the idea and its line: the sort, the reason in one sentence, the size (small, medium or large). Each option's description repeats its sort's effect. Print no line before the menu.
- now: joins the active milestone.
- next, later: go into the backlog; next is the following milestone, later is someday.
VBW's sort is the first option, marked (Recommended); the two other sorts are the other options. Never ask the user to type a command. Up to four ideas per menu; more than four are sorted four at a time. During a run, sort without interrupting it; a "now" idea waits for the run to end.
Outcomes
- now:
vbw spec add auto|human "<idea>", then the normal flow (planning again, the approval menu). No active milestone:vbw milestone start "<title>"with the idea as its first requirement. - next or later:
vbw todo add --sort <sort> --size <size> "<idea>".
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 · 51 lines · 43 tokens per session scan A dec4e6561370
triage 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 43 tokens to every session and 791 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,"…