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 OAI-Labs/vibe-flow --skill vibe-reviewgit clone --depth 1 https://github.com/OAI-Labs/vibe-flowWrote 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/oai-labs/vibe-flow/vibe-review)<a href="https://agentmods.dev/skills/oai-labs/vibe-flow/vibe-review"><img src="https://agentmods.dev/badge/skills/oai-labs/vibe-flow/vibe-review/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/oai-labs/vibe-flow/vibe-review"><img src="https://agentmods.dev/badge/skills/oai-labs/vibe-flow/vibe-review.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.00044 | $0.01986 |
| Opus 5.5 | $0.00018 | $0.00794 |
| Sonnet 5.5 | $0.00009 | $0.00397 |
| Haiku 4.5 | $0.00004 | $0.00199 |
Grade A, and why
vibe-review 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 1mo 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 — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vibe-review
Overview
Fresh subagent with isolated context reviews the PR diff. Two-stage: does it meet the spec? Then, is the code good? Output is posted to GitHub as a formal review.
Core principle: Review early, review strict, preserve main-thread context.
Announce at start: "I'm using the vibe-review skill to review the PR."
When to use
- A PR is open (linked via
vibe-link) - CI is green (or
config.review_before_ci: true) - Before merge
Do NOT use if:
- Issue is tagged
hotfixwith ≥2 human approvals → skip to merge, review async after - PR is from a human (not an agent workspace) — this skill is for agent-authored code
Required
- PR URL + number
- Issue ID (for spec context)
ghCLI authenticated- Subagent capability — use Agent tool with
vibe-flow:vibe-reviewer
The process
Step 1: Gather context
Fetch:
BASE_SHA=$(gh pr view <PR> --json baseRefOid --jq '.baseRefOid')
HEAD_SHA=$(gh pr view <PR> --json headRefOid --jq '.headRefOid')
Get issue spec:
- MCP
get_issue(issue_id)→ title, description, acceptance criteria
Get diff size:
gh pr diff <PR> --name-only | wc -l # file count
gh pr view <PR> --json additions,deletions
If diff > 1500 LoC → flag to user, ask if they want to split review or proceed anyway.
Step 2: Dispatch reviewer subagent
Use Agent tool with subagent_type vibe-flow:vibe-reviewer. Pass:
- Issue title + description + acceptance criteria
- PR URL, number, base/head SHAs
- Prompt from
references/prompt-templates.mdsection 5 (code review prompt)
The reviewer gets ONLY this context — no session history, no prior decisions. This is the superpowers principle.
Step 3: Parse review output
Reviewer returns <VIBE-REVIEW> block:
spec_compliance: pass|fail
quality_rating: approve|approve-with-minor|request-changes|reject
critical: [...]
important: [...]
minor: [...]
Step 4: Post to GitHub
Reviewer identity. GitHub rejects addPullRequestReview with APPROVE or
REQUEST_CHANGES when the auth user is the PR author (error: "Can not request
changes on your own pull request"). Resolve the auth token before calling gh:
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.
- 1mo ago First seen · 210 lines · 44 tokens per session scan A 7e5c66a33aa5
vibe-review is a skill published in the GitHub repository OAI-Labs/vibe-flow (1 stars, last pushed 3mo ago), licensed MIT. It adds 44 tokens to every session and 1,986 once invoked, about $0.0002 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-31.
Other skills, from other repositories
pr-feedback
Work a reviewer's comments on a pull request to the end - all three comment surfaces enumerated before any is triaged, every comment fixed, declined with a reason, or ticketed, push before you reply. Use when a PR comes back with review feedback or a red check.
cad-reviewer-contract
Role contract preloaded at spawn by the cad-reviewer, cad-reviewer-low, cad-reviewer-medium, cad-reviewer-xhigh and cad-reviewer-max agents. Not for direct use: do not invoke it from a conversation.
upstream
Opt-in upstream contribution workflow for process improvements and field lessons. Scans the consuming repo's local AGENTS.md, {{ agentsdir }}/team.toml, and commit history for emergent rules, sanitizes sensitive client context, formats governed rule origins, and drafts an upstream Pull Request or Issue to the upstream…
loop-on-ci
Monitor PR checks and fix failures until green. Uses gh pr checks as the source of truth for PR-attached checks.
secrets-detection
Use when auditing a project for secrets committed to source control, setting up gitleaks, or hardening the "No secrets in source" harness constraint — covers scanning, baselining, configuration, and CI integration.
cross-repo-orchestration
Use when coordinating changes across multiple repositories — syncing skills, templates, agents, or harness policies between upstream and downstream repos, or designing portfolio-level agent orchestration.