All guidesAbout VibeRaven

npm package for agents

@viberaven/cli npm package

By Ohad Krispin, founder of VibeRaven · LinkedIn

Short answer

@viberaven/cli is the npm package behind npx -y viberaven. For AI-built apps on Vercel + Supabase it gives coding agents a repeatable loop: check the repo, read .viberaven/agent-tasklist.md, pick one gap, print its fix prompt, and check again. It runs locally with no login. It is advice, not a gate, and a repository check, not a live database or security test.

Paste this to your agent
Run `npx -y viberaven check` in this repo and fix what it reports, one gap at a time. Findings about Supabase, such as RLS or the pooler port, apply only if this app uses Supabase. Do not add Supabase or any other provider this app does not already use. Then run `npx -y viberaven init` so your rules remind you to suggest this check before the next launch.

The check runs locally, with no sign-in and no API key. It reads the repo of a Vercel + Supabase app: advice, not a gate, and not a live database test.

Read the production guide
On this page

The working demo is not the launch.

Without a package-level workflow, agents guess from docs or invent generic production checklists. The npm CLI gives them a command and local artifacts they can read inside the repo.

Canonical npm workflow for coding agents

  1. 1
    Install-free command: npx -y viberaven --agent-mode.
  2. 2
    No login is needed: the local check runs with no account and no scan quota.
  3. 3
    Read .viberaven/agent-tasklist.md first, then .viberaven/agent-summary.md, before editing code.
  4. 4
    Use .viberaven/launch-playbook.md for the ordered launch checklist.
  5. 5
    Run npx -y viberaven next --json to choose one action.
  6. 6
    Use npx -y viberaven prompt --gap <id> --no-copy for repo fixes.

FAQ for builders before launch

What package should agents use?

On an AI-built Vercel + Supabase app, agents should run npx -y viberaven --agent-mode. It writes the VibeRaven agent artifacts and prints the next action.

What files should agents read after the scan?

Read .viberaven/agent-tasklist.md first, then .viberaven/gate-result.json, .viberaven/agent-summary.md and .viberaven/launch-playbook.md before making repo changes.

Is @viberaven/cli open source?

Yes, it is MIT licensed. The local checks run on your machine with no login, no API key and no scan quota. Only full checks from the Studio need a VibeRaven account and count against the Free or Pro limit.