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/xushuodasd/VIBE-Claude-PluginWrote 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/commands/xushuodasd/vibe-claude-plugin/vibe)<a href="https://agentmods.dev/commands/xushuodasd/vibe-claude-plugin/vibe"><img src="https://agentmods.dev/badge/commands/xushuodasd/vibe-claude-plugin/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/commands/xushuodasd/vibe-claude-plugin/vibe"><img src="https://agentmods.dev/badge/commands/xushuodasd/vibe-claude-plugin/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.00028 | $0.00242 |
| Opus 5 | $0.00014 | $0.00121 |
| Sonnet 5 | $0.00006 | $0.00048 |
| Haiku 4.5 | $0.00003 | $0.00024 |
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 9d ago.
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
/vibe Command
Start the VIBE autonomous engineering workflow.
Usage
/vibe <your project requirement>
What This Command Does
When a user runs /vibe, the command should:
- Trigger the
vibe-autopilotskill. - Start with requirement analysis and architecture planning, then generate artifacts such as the PRD, architecture notes, database notes, and
tasks.md. - After the user approves the plan, continue through the execution loop:
- requirement analysis
- architecture design
- task breakdown
- iterative implementation with isolated sub-tasks
- testing
- security review
- UI polish
- E2E real browser verification
- delivery
- During execution, minimize interruptions and keep moving with the best available option.
If No Requirement Is Provided
If the user only types /vibe, begin requirement discovery. Ask about the project goal, core features, preferred stack, and UI direction.
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.
- 9d ago First seen · 37 lines · 28 tokens per session scan A 679aedda88e7
vibe is a command published in the GitHub repository xushuodasd/VIBE-Claude-Plugin (4 stars, last pushed 2mo ago), licensed MIT. It adds 28 tokens to every session and 242 once invoked, about $0.0001 per session on Opus 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-08-31.
Other commands, from other repositories
execute
Execute the next available tracked task with TDD, pre-commit validation, PR creation, AI code review, and issue tracker bridge sync.
loop
Autonomous execution loop. Runs the TDD cycle repeatedly until all tasks in an epic are complete, with circuit breaker protection and PR workflow.
phase
Orchestrate a full roadmap phase. Designs features, imports to tracker, creates issues, then executes.
dashboard
Compact visual progress dashboard with progress bar, task table, dependency graph, and active/blocked/next status.
sync
Reconcile coco tracker state with the configured issue tracker. Syncs task statuses and reports mismatches.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.