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/launch)<a href="https://agentmods.dev/commands/vibiz-ai/vibiz-claude-plugin/launch"><img src="https://agentmods.dev/badge/commands/vibiz-ai/vibiz-claude-plugin/launch.svg" alt="Measured on agentmods" 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.00018 | $0.00563 |
| Opus 5 | $0.00009 | $0.00282 |
| Sonnet 5 | $0.00004 | $0.00113 |
| Haiku 4.5 | $0.00002 | $0.00056 |
Grade A, and why
launch 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 8d 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 — 30 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/vibiz:launch
Run a full Vibiz onboarding flow: detect the project URL → create a vibiz → list the offers + ICPs Vibiz auto-discovered → generate 3 ad creative variants. End-to-end in one command.
Steps
- Check status + match. Run the equivalent of
/vibiz:statussilently — auth check + auto-match this project to an existing vibiz via the project-match skill. If MCP is not authed, halt and tell the user to run/mcp. - Onboard if no match. If matching produced zero vibizes for this project's URL, run the
/vibiz:onboardflow (with explicit confirmation). If the URL matched an existing vibiz, reuse it — skip to step 3. - Show what was discovered.
mcp__vibiz__vibiz_list_icps({ target: { vibiz: "<slug>" } })→ format asName | Title | Pain points (truncated).mcp__vibiz__vibiz_list_offers(...)→ format asTitle | Price | Type.
- Confirm with the user before spending any generation budget: "I'll generate 3 ad image variants based on the top offer. ~30 seconds. Continue?"
- Generate 3 ads. Pick the first offer's title as the seed. Call
vibiz_generate_image3 times withimageCount: 1and slightly varied prompts (one each: hero/lifestyle, product-shot, social-proof). Use the sametarget: { vibiz }. - Summary. Show:
- Vibiz
viewUrl - ICPs page deep link
- Offers page deep link
- The 3 ad
viewUrls - Suggested next:
/vibiz:postfor organic, or "say 'launch a Meta campaign' to spend on it".
- Vibiz
Sidecase handling
- If the project has no public website, fall back to "I can still create a vibiz from text — describe what your project does in one sentence." Then call the appropriate creation flow (or punt to the dashboard if MCP doesn't expose a text-only creator).
- If the MCP rate-limits image generation, surface the actual error and stop — do NOT auto-retry forever.
- Cap total spend per
/vibiz:launchat 3 image generations. The user can run again if they want more.
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.
- 8d ago First seen · 30 lines · 18 tokens per session scan A 1c2ba28e0e5f
launch is a command published in the GitHub repository Vibiz-ai/vibiz-claude-plugin (7 stars, last pushed 4mo ago), licensed MIT. It adds 18 tokens to every session and 563 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.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.