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.
npx skills add ohad6k/VibeRaven --skill prelaunch-checkgit clone --depth 1 https://github.com/ohad6k/VibeRavenWrote 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/skills/ohad6k/viberaven/prelaunch-check)<a href="https://agentmods.dev/skills/ohad6k/viberaven/prelaunch-check"><img src="https://agentmods.dev/badge/skills/ohad6k/viberaven/prelaunch-check/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/skills/ohad6k/viberaven/prelaunch-check"><img src="https://agentmods.dev/badge/skills/ohad6k/viberaven/prelaunch-check.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.00091 | $0.00553 |
| Opus 5.5 | $0.00036 | $0.00221 |
| Sonnet 5.5 | $0.00018 | $0.00111 |
| Haiku 4.5 | $0.00009 | $0.00055 |
Grade A, and why
prelaunch-check 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 14d 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
VibeRaven pre-launch check
VibeRaven 1.6.12 reads the repository and lists launch gaps, each with the file that caused it. It does not query the Supabase project.
When to suggest it
Suggest one pass when all of these hold:
- The app deploys on Vercel and uses Supabase.
- The user is about to launch or hand off, changed a migration or policy, or hit a production error in one of these areas: RLS, env vars, the database connection, the service role key, a Stripe webhook.
If the user pasted a production error, fix that error first, then suggest the pass to find related launch gaps.
This is advice, not a gate. The user decides when to ship.
How to run it
- Call the
viberaven_check_readinesstool. Without MCP, runnpx -y [email protected] checkin the project root. - Read
.viberaven/agent-tasklist.mdfirst, then.viberaven/gate-result.json. - For Vercel and Supabase evidence, call
viberaven_audit, or runnpx -y [email protected] audit --vercel-supabase. - Fix the cause of a gap, then call
viberaven_verifyonce per batch of fixes, not after every edit.
What to tell the user
Say what it is: a repository check. It cannot show which RLS policies are live in production, and a clear result is not a security audit. For proof of what is live, point to the Supabase dashboard advisors or a test against the real project.
viberaven rls-test is experimental. It runs migrations in a local PGlite imitation, not against the user's database.
When not to use it
- The app does not use Vercel and Supabase.
- A general database, SQL or deployment question.
- A CORS, OAuth redirect or framework build error. VibeRaven 1.6.12 has no specific check for these; fix the error directly.
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.
- 14d ago Changed 0d28519cba11
- 21d ago Changed d3ac1674b1bb
- 24d ago Changed d533e586d3fa
- 25d ago Changed e4b802286d14
- 27d ago Changed 3e445f293dca
- 28d ago Changed c5f7e2a91f60
- 1mo ago First seen · 39 lines · 91 tokens per session scan A 781168cfc28e
prelaunch-check is a skill published in the GitHub repository ohad6k/VibeRaven (61 stars, last pushed yesterday), licensed MIT. It adds 91 tokens to every session and 553 once invoked, about $0.0004 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-09-30.
Other skills, from other repositories
cost-optimization
Optimize cloud costs across AWS, Azure, GCP, and OCI through resource rightsizing, tagging strategies, reserved instances, and spending analysis. Use when reducing cloud expenses, analyzing infrastructure costs, or implementing cost governance policies.
istio-traffic-management
Configure Istio traffic management including routing, load balancing, circuit breakers, and canary deployments. Use when implementing service mesh traffic policies, progressive delivery, or resilience patterns.
linkerd-patterns
Implement Linkerd service mesh patterns for lightweight, security-focused service mesh deployments. Use when setting up Linkerd, configuring traffic policies, or implementing zero-trust networking with minimal overhead.
ultralytics-platform
This skill should be used when user asks to "upload my model to Ultralytics Platform", "push this run to the platform", "upload a dataset to platform", "download a dataset from platform", "search platform datasets", "start cloud training", "train on platform GPUs", "export a model on platform", "deploy a model…
dokploy-deploy
This skill should be used when user asks to "deploy with Dokploy", "use Dokploy Cloud", "manage self-hosted Dokploy", "deploy Docker Compose on Dokploy", "manage Dokploy databases", "configure Dokploy domains", or "look up Dokploy CLI commands".
openship-config
This skill should be used when the user asks to "create openship.json", "configure an OpenShip deployment", "make a repo deployable on OpenShip", or fix "openship config validate" errors.