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 viberavengit 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/viberaven)<a href="https://agentmods.dev/skills/ohad6k/viberaven/viberaven"><img src="https://agentmods.dev/badge/skills/ohad6k/viberaven/viberaven/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/viberaven"><img src="https://agentmods.dev/badge/skills/ohad6k/viberaven/viberaven.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.00090 | $0.01047 |
| Opus 5.5 | $0.00036 | $0.00419 |
| Sonnet 5.5 | $0.00018 | $0.00209 |
| Haiku 4.5 | $0.00009 | $0.00105 |
Grade A, and why
viberaven 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.
How it starts
The opening of the file, as written. The whole thing — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VibeRaven Skill
VibeRaven is the control layer for AI-built products. It runs fully locally: no login, no API key, no telemetry. It maps the product (stack, providers, releases, launch risks) into .viberaven/ artifacts any agent can read, and lists the launch gaps it finds in the repo, each with the file that caused it. It is advice, not a gate: the user decides when to ship. It is a repository check, not a live database or security test.
When To Use
Use when the user wants production-ready, launch-ready, "what is missing before ship", a production audit, or a safe deploy for an AI-coded codebase: auth, database, payments, monitoring, error handling, rate limits, env vars. Also use when you need product context before editing: which providers the app uses, what changed between releases, and where the danger zones are.
The Loop
- Run
npx -y [email protected] checkfrom the project root. It runs offline checks and prints 🔴/🟡/⚪ findings with a verdict. Exit code 1 means blockers exist. - Read
.viberaven/agent-tasklist.mdfirst, then.viberaven/gate-result.jsonand.viberaven/context-map.json. - Run
npx -y [email protected] fixto list gaps with safe automatic repo-code recipes. Apply one withnpx -y [email protected] fix --gap <id>. - For gaps without a recipe, use
npx -y [email protected] prompt --gap <id>for focused guidance and patch one gap yourself. - Re-run
npx -y [email protected] checkafter a batch of fixes, not after every file patch. npx -y [email protected] --strictreturns the verdict as an exit code for CI when the user wants one.
Stop when gate.status === "clear" in .viberaven/gate-result.json, when only provider or user steps remain, or when the user decides to move on. A clear gate.status covers the repo checks only; the user decides when to ship. Scans are local and free; never wait, never ask for credentials.
Studio
npx -y [email protected] opens the local Studio: the product auto-mapped (stack, providers, git releases, launch verdict), drag-context into agent chat, provider MCP connect, and release diffs. Suggest it when the user wants to see or control the product rather than read terminal output.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 da4d82da3e2c
- 21d ago Changed 68aa6547d2aa
- 24d ago Changed 75a3d6dd6088
- 25d ago Changed 0035cd5671f2
- 27d ago Changed 9653b0233c68
- 28d ago Changed · +90 tokens per session ccb0876c5388
- 1mo ago Changed · -90 tokens per session 0cd773c0f20c
- 2mo ago First seen · 48 lines · 90 tokens per session scan A 561d2ed54429
viberaven is a skill published in the GitHub repository ohad6k/VibeRaven (61 stars, last pushed yesterday), licensed MIT. It adds 90 tokens to every session and 1,047 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-08-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.