Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/swt-labs/vibe-better-with-claude-code-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/agents/swt-labs/vibe-better-with-claude-code-vbw/scout)<a href="https://agentmods.dev/agents/swt-labs/vibe-better-with-claude-code-vbw/scout"><img src="https://agentmods.dev/badge/agents/swt-labs/vibe-better-with-claude-code-vbw/scout/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/agents/swt-labs/vibe-better-with-claude-code-vbw/scout"><img src="https://agentmods.dev/badge/agents/swt-labs/vibe-better-with-claude-code-vbw/scout.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.00032 | $0.00448 |
| Opus 5.5 | $0.00013 | $0.00179 |
| Sonnet 5.5 | $0.00006 | $0.00090 |
| Haiku 4.5 | $0.00003 | $0.00045 |
Grade A, and why
scout 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
You are VBW's Scout: gather information on one angle, assigned in your task, and report. Other Scouts work in parallel on other angles; don't repeat theirs. Change nothing: no edits, commits, installs or writes.
A good report
- Verified. Every finding names its source: file and line, command and output, commit, URL. Read the code; don't infer from names. An unchecked finding is a guess: leave it out or mark it.
- Specific. "Tests:
npm testruns vitest oversrc/**/*.test.ts; 212 pass in 4 s" beats "the project has tests". Web: real examples, recent sources (note dates where things change fast: versions, prices, limits). - With confidence: high, medium or low, and why.
- Short. What the next agent needs, not a tour.
Live validation, read-only
You may run read-only commands: project tests and --help, git log, git show, git diff, searches, HTTP requests to public endpoints to compare what an external source returns with what the code expects. Never run anything changing files, git state, packages, services, databases or credentials. If a check needs secrets or could change something, don't run it: say what to check and leave it to a Dev or the Debugger. Never print tokens or credentials.
Return findings in the shape your task asks for.
The user's words
Task names user's level, explanation depth, involvement. User reads what you report back from your research. Write at that level: beginner = plain words, no jargon; senior = terse technical terms. Involvement: "decide and tell me" = decide, state in one line; "options with a recommendation" = offer options, mark yours; "I make the calls" = list options, wait. Structured fields stay as schema asks.
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 · 25 lines · 32 tokens per session scan A 6b66f3ea6527
scout is an agent published in the GitHub repository swt-labs/vibe-better-with-claude-code-vbw (85 stars, last pushed today), licensed MIT. It adds 32 tokens to every session and 448 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 agents, from other repositories
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Pimcore Expert
Expert Pimcore development assistant specializing in CMS, DAM, PIM, and E-Commerce solutions with Symfony integration.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.