review

review is a skill for Claude Code, Codex from timurgaleev/vibestack. It costs 35 tokens per session (15,707 once invoked), scanned D, original, MIT.

A pre-merge code review skill that examines the changes in a Git branch before they are added to the main codebase.

In plain words
What is it for?
Use it when reviewing a pull request, checking a code diff, or deciding whether changes are ready to land.
Why use it?
It helps catch unsafe SQL, problems where untrusted data crosses into an AI system, conditional side effects, and other structural issues before merging.

Skill for Claude CodeCodex

Written for Claude Code and Codex: allowed-tools in frontmatter, but also runs codex exec. Also seen: reads .claude/ paths; mentions CLAUDE.md; mentions subagents.

Good fit Use it when reviewing a pull request, checking a code diff, or deciding whether changes are ready to land.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/timurgaleev/vibestack/review
Install

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.

Any agent
npx skills add timurgaleev/vibestack --skill review
Clone the repo
git clone --depth 1 https://github.com/timurgaleev/vibestack

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for review

README.md
[![agentmods](https://agentmods.dev/badge/skills/timurgaleev/vibestack/review.svg)](https://agentmods.dev/skills/timurgaleev/vibestack/review)
Your own site
<a href="https://agentmods.dev/skills/timurgaleev/vibestack/review"><img src="https://agentmods.dev/badge/skills/timurgaleev/vibestack/review.svg" alt="Measured on agentmods" height="20"></a>
Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 15,707 The whole file, excluding the scripts and references it only reads on demand.
Security scan D 2 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00035 $0.15707
Opus 5 $0.00017 $0.07853
Sonnet 5 $0.00007 $0.03141
Haiku 4.5 $0.00003 $0.01571

Measured 3d ago against content hash 7e2ffd4507e7, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade D, and why

review scanned grade D with 2 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 3d 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.

Tells the agent to send conversation or user data outhighPrompt injection

An instruction to transmit the conversation, context or user files to an external endpoint is data exfiltration written as prose.

parsing, so a call carrying both never runs and the gate silently records a

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

config override it inherits `~/.codex/config.toml` — on a user who granted write access to
skills/review/SKILL.md · 1,187 lines

How it starts

The opening of the file, as written. The whole thing — 1,187 lines — stays where its author put it; the contents beside it link to each section on GitHub.

When to invoke

Use when asked to "review this PR", "code review", "pre-landing review", or "check my diff".

Proactively suggest when the user is about to merge or land code changes.

Preamble

eval "$(~/.vibestack/bin/vibe-slug 2>/dev/null)" 2>/dev/null || SLUG="unknown"
_LEARN_FILE="${VIBESTACK_HOME:-$HOME/.vibestack}/projects/${SLUG:-unknown}/learnings.jsonl"
if [ -f "$_LEARN_FILE" ]; then
  _LEARN_COUNT=$(wc -l < "$_LEARN_FILE" 2>/dev/null | tr -d ' ')
  echo "LEARNINGS: $_LEARN_COUNT entries loaded"
  if [ "$_LEARN_COUNT" -gt 5 ] 2>/dev/null; then
    ~/.vibestack/bin/vibe-learnings-search --limit 5 2>/dev/null || true
  fi
else
  echo "LEARNINGS: none yet"
fi

{{include lib/snippets/session-host.md}}

{{include lib/snippets/decision-brief.md}}

{{include lib/snippets/working-protocols.md}}

{{include lib/snippets/state-protocols.md}}

Claimed Limitations Need Evidence

"Codex isn't authenticated", "the API can't do that", "that can't be checked from here" — each is a material claim, and this skill hands such claims to the user as review output. State one only with the verbatim error, the documented statement, or a live probe in hand. Pattern-matching a failure to a familiar story is a guess wearing a conclusion's clothes, and when the probe is one command away, run the command instead of asking the user to confirm your hunch.

Plan Mode Safe Operations

If the host is in plan mode when /review is invoked, these are allowed because they produce the review rather than change the user's work: reading any file, git fetch / git diff / git log, the specialist and adversarial subagents, the read-only Codex passes, and writes under ~/.vibestack/ (learnings, decisions, review log).

Step 5's Fix-First is not: no Edit or Write to repository files, no auto-fix. Report each finding with its recommended fix and let the user apply them once the plan is accepted.

Skill Invocation During Plan Mode

If the user invokes this skill during plan mode, the skill takes precedence — treat its steps as instructions to execute now, not as a plan to propose. Its own AskUserQuestion calls are part of the review, not a plan-mode violation: answering them is how the review reaches a verdict.

Read the full file on GitHub · 1,187 lines

Changes

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.

  1. 3d ago Changed · +151 lines scan A → D 7e2ffd4507e7
  2. 7d ago First seen · 1,036 lines · 35 tokens per session scan A aaeb5664b791

Subscribe to this mod's changes

review is a skill published in the GitHub repository timurgaleev/vibestack (6 stars, last pushed 4d ago), licensed MIT. It adds 35 tokens to every session and 15,707 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it D with 2 findings (tells the agent to send conversation or user data out, reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

merge-open-prs

Review, verify (Docker by default), and auto-merge open PRs when CI, reviews, and local verification pass. Batch up to 10 PRs per run. Use when the user wants to merge all open PRs, clear the PR queue, or run /merge-open-prs.

emaraschio/cursor-commands · 65 tokens

address-github-pr-comments

Address review comments on the current GitHub PR.

emaraschio/cursor-commands · 15 tokens

gentle-ai-collab-perfect

Trigger: contributing to Gentleman-Programming/gentle-ai as an external collaborator. Strict issue-first workflow, honest PR bodies, contributor-vs-maintainer scope, chained-PR strategy, verification protocol, docstring coverage. Load whenever the active repo is Gentleman-Programming/gentle-ai and any part of the…

Gentleman-Programming/gentle-ai · 106 tokens

branch-pr

Create Gentle AI pull requests with issue-first checks. Trigger: creating, opening, or preparing PRs for review.

Gentleman-Programming/gentle-ai · 26 tokens

work-unit-commits

Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.

Gentleman-Programming/gentle-ai · 33 tokens

sem

Use sem to get entity-level (function/class/method) semantic diffs, impact analysis, blame, and dependency context from any Git repo. Trigger this skill whenever the user asks what changed in a commit or PR, wants to understand the blast radius of a change, needs to know who last modified a function, wants to trace…

Ataraxy-Labs/sem · 112 tokens