A command that registers the current project as a Vibiz brand, where a Vibiz stores a company’s brand details, target customers, and offers.

Use it to find the project’s website, match it to an existing Vibiz, or—with confirmation—scrape the site and create a new brand record.

It prevents duplicate brand records by checking whether the project already has a matching Vibiz before creating one.

onboard — Command for Claude Code by Vibiz-ai

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/onboard/github.svg)](https://agentmods.dev/commands/vibiz-ai/vibiz-claude-plugin/onboard)

Your own site

<a href="https://agentmods.dev/commands/vibiz-ai/vibiz-claude-plugin/onboard"><img src="https://agentmods.dev/badge/commands/vibiz-ai/vibiz-claude-plugin/onboard/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/onboard"><img src="https://agentmods.dev/badge/commands/vibiz-ai/vibiz-claude-plugin/onboard.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 741 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.00024	$0.00741
Opus 5	$0.00012	$0.00370
Sonnet 5	$0.00005	$0.00148
Haiku 4.5	$0.00002	$0.00074

Measured 11d ago against content hash 44c6412d7ee9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

onboard 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 11d 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/onboard.md · 51 lines

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.

/vibiz:onboard

End-to-end flow: detect this project's URL → check for an existing vibiz → only create a new one if no match.

Steps

MCP gate. Try list_vibiz. If unauthed → tell user /mcp → vibiz → Authenticate → re-run. Stop.
Detect this project's brand URL using the project-match skill. Same fallback chain: package.json homepage → pyproject.toml / Cargo.toml → first non-badge non-github link in README → ask user.
Match against existing vibizes (using normalized websiteUrl comparison from the project-match skill).
Branch on the match outcome:

Existing match found → tell the user, do NOT create another.
```
✓ Found an existing vibiz for <url>: "<name>" (slug: <slug>)
   Reusing it. To force-create a new one, say: /vibiz:onboard --force <url>
```
Then list ICPs + offers from that vibiz so the user knows what's already in there.

No match → confirm with the user before creating:
```
I'll scrape <url> and create a new vibiz from it. This:
  - generates a brand kit (colors, fonts, logo, voice)
  - auto-discovers ICPs and offers
  - takes ~30 seconds
Sound good? (yes / no / use a different URL)
```
On yes → call vibiz_create_from_url({ websiteUrl: "<url>" }). Show the returned viewUrl. Tell the user the slug for use on later commands.

No URL detected → ask: "Paste the public URL for this project, or skip."
Optional follow-up. Once a vibiz is matched OR created, ask:

Want me to (1) generate 3 ad variants now, or (2) draft a launch post about your latest commit? Map answers to /vibiz:launch and /vibiz:post respectively.

Sidecase handling

Local / private URLs (localhost, 127.0.0.1, *.internal, *.local, *.test) → refuse, explain the brand kit needs a public URL.
--force <url> flag in $1 → skip the matching step, go straight to vibiz_create_from_url. Useful when the detected URL was wrong.
GitHub repo with no clear product site → ask the user explicitly. Don't silently use the GitHub URL as the brand URL — that's almost never what they want.
Existing match but it's clearly the wrong vibiz (user says "no, that's a different brand") → suggest /vibiz:onboard --force <correct-url>.
Trigger.dev task fails → surface the error verbatim, do not retry, do not pretend it succeeded.

Read the full file on GitHub · 51 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.

11d ago First seen · 51 lines · 24 tokens per session scan A 44c6412d7ee9

Subscribe to this mod's changes

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

Marketing and SEO

onboard

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

/vibiz:onboard

Steps

Sidecase handling

What this file has done since we first saw it

Other commands, from other repositories

checklist

clarify

specify

analyze

converge

implement