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/Vibiz-ai/vibiz-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/vibiz-ai/vibiz-claude-plugin/status)<a href="https://agentmods.dev/commands/vibiz-ai/vibiz-claude-plugin/status"><img src="https://agentmods.dev/badge/commands/vibiz-ai/vibiz-claude-plugin/status/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/vibiz-ai/vibiz-claude-plugin/status"><img src="https://agentmods.dev/badge/commands/vibiz-ai/vibiz-claude-plugin/status.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.00017 | $0.00708 |
| Opus 5 | $0.00009 | $0.00354 |
| Sonnet 5 | $0.00003 | $0.00142 |
| Haiku 4.5 | $0.00002 | $0.00071 |
Grade A, and why
status 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.
How it starts
The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/vibiz:status
Verify the MCP is authenticated and try to match the current local project to one of the user's vibizes. This is usually the first command the user runs.
Steps
-
Try
list_vibiz. If it fails withUnauthorized/not authenticated:- Tell the user to run
/mcp, pickvibiz, choose Authenticate, finish the browser login, then re-run/vibiz:status. - Stop here — do nothing else.
- Tell the user to run
-
Detect this project's brand URL using the project-match skill:
- Try
package.jsonhomepage, thenpyproject.toml/Cargo.tomlhomepage, then the first non-badge non-github link in the README. - Skip private / local URLs.
- Try
-
Match the detected URL against each vibiz's
websiteUrlfrom step 1, after normalizing both sides (lowercase, strip protocol/www/trailing-slash, host + first path segment only). -
Report. Output is one of:
A. MCP not authed
❌ Vibiz MCP — not authenticated. Run /mcp → vibiz → Authenticate.B. No vibizes at all
✓ Vibiz MCP — connected ⚠ You don't have any vibizes yet. Run /vibiz:onboard to create one from this project, or sign up at https://vibiz.ai.C. Project URL detected, exact match found
✓ Vibiz MCP — connected ✓ Matched this project (<detected-url>) → vibiz "<name>" (slug: <slug>) Subsequent /vibiz commands will scope to this vibiz automatically. Other vibizes available: <name1>, <name2>, …D. Project URL detected, NO match
✓ Vibiz MCP — connected ⚠ This project (<detected-url>) is not yet onboarded as a vibiz. Available vibizes: <name1>, <name2>, … Run /vibiz:onboard to create a new one for this project, or pick one of the above by name.E. No detectable URL
✓ Vibiz MCP — connected Available vibizes: <name1>, <name2>, … I couldn't auto-detect a brand URL from this repo (no package.json homepage, no obvious link in README). Tell me which vibiz to use, or run /vibiz:onboard with a URL. -
Remember the matched slug for this session — quote it explicitly in your message ("using vibiz
<slug>for the rest of this session") so subsequent tool calls inherit the choice.
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 · 60 lines · 17 tokens per session scan A 1841231dab10
status is a command published in the GitHub repository Vibiz-ai/vibiz-claude-plugin (7 stars, last pushed 4mo ago), licensed MIT. It adds 17 tokens to every session and 708 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.