A command for checking the connection to Vibiz, a service for managing brand workspaces, and matching the current project to one of them. It reports whether authentication, available workspaces and project matching succeeded.

Use it at the start of Vibiz work to verify access, detect the project's website address and find its matching brand workspace.

It gives a quick status check before using Vibiz features and explains what to do if the connection is not authenticated or no workspace exists.

status — Command for Claude Code by Vibiz-ai/vibiz-claude-plugin

Install

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.

Clone the repo

git clone --depth 1 https://github.com/Vibiz-ai/vibiz-claude-plugin

Made for: Claude Code.

Or install vibiz, the plugin that ships this one along with the rest of its 2 skills, 7 commands, 1 agent, 1 hook, 1 MCP server.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/vibiz-ai/vibiz-claude-plugin/status/github.svg)](https://agentmods.dev/commands/vibiz-ai/vibiz-claude-plugin/status)

Your own site

<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.

Your own site · 80×15

<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>

Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 708 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.5	$0.00007	$0.00283
Sonnet 5.5	$0.00003	$0.00142
Haiku 4.5	$0.00002	$0.00071

Measured 2mo ago against content hash 1841231dab10, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

plugins/vibiz/commands/status.md · 60 lines

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 with Unauthorized / not authenticated:
- Tell the user to run /mcp, pick vibiz, choose Authenticate, finish the browser login, then re-run /vibiz:status.
- Stop here — do nothing else.
Detect this project's brand URL using the project-match skill:
- Try package.json homepage, then pyproject.toml / Cargo.toml homepage, then the first non-badge non-github link in the README.
- Skip private / local URLs.
Match the detected URL against each vibiz's websiteUrl from 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.

Read the full file on GitHub · 60 lines

Changes

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.

2mo ago First seen · 60 lines · 17 tokens per session scan A 1841231dab10

Subscribe to this mod's changes

status is a command published in the GitHub repository Vibiz-ai/vibiz-claude-plugin (7 stars, last pushed 6mo ago), licensed MIT. It adds 17 tokens to every session and 708 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-08-31.

status next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
statusVibiz-ai/vibiz-claude-plugin	Command	7	6mo ago	MIT	A	17	Claude Code
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	yesterday	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	yesterday	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	yesterday	MIT	A	14	Claude Code