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 happy-nut/claude-plugin-viban --skill reviewgit clone --depth 1 https://github.com/happy-nut/claude-plugin-vibanWrote 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/happy-nut/claude-plugin-viban/review)<a href="https://agentmods.dev/skills/happy-nut/claude-plugin-viban/review"><img src="https://agentmods.dev/badge/skills/happy-nut/claude-plugin-viban/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/happy-nut/claude-plugin-viban/review"><img src="https://agentmods.dev/badge/skills/happy-nut/claude-plugin-viban/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.00012 | $0.00623 |
| Opus 5 | $0.00006 | $0.00311 |
| Sonnet 5 | $0.00002 | $0.00125 |
| Haiku 4.5 | $0.00001 | $0.00062 |
Grade A, and why
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 9d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/review
Checkout a review-status issue's branch into the main worktree so the user can review all changes as staged diffs in their IDE.
CLI only (no direct viban.json access)
Input: $ARGUMENTS (optional: issue ID)
Output Rules
- Do NOT output any preamble. No "Your Task:", "I'll now...", "Let me...", or task summaries before starting work.
- Start executing Step 1 immediately and silently.
Step 1: Find Review Card
If $ARGUMENTS contains an issue ID, use it. Otherwise find the first review card:
viban list --status review
If no review cards exist, tell the user and exit.
Extract the issue ID. Store as $ID.
viban get $ID
Show the user a one-line summary: #ID [PRIORITY] Title.
Step 2: Prepare Branch
BRANCH="issue-$ID"
WT_DIR="$PWD/.viban/worktrees/$ID"
If worktree exists, detach it to free the branch:
[ -d "$WT_DIR" ] && git -C "$WT_DIR" checkout --detach 2>/dev/null
Step 3: Handle Dirty Working Tree
git status --porcelain
If dirty, ask user with AskUserQuestion:
- "You have uncommitted changes. How should we save them?"
- Options:
- "Stash" →
git stash push -m "viban-review: before #$ID" - "Temp commit" →
git add -A && git commit -m "viban-review: temp commit before #$ID"
- "Stash" →
If clean, proceed directly.
Step 4: Detached Checkout and Reset
git checkout --detach "$BRANCH"
git reset --soft main
This checks out the branch's commit without moving the branch pointer. Now all changes appear as staged diffs in the IDE, and the $BRANCH ref stays intact.
Step 5: Report and Exit
PR_INFO=$(gh pr list --head "$BRANCH" --json number,url --jq '.[0]' 2>/dev/null)
Tell the user:
Reviewing #$ID — all changes are staged in your IDE.
{PR #N: <url> if PR exists}
Run /viban:approve $ID or /viban:reject $ID when ready.
Done. Do not wait for user input. The skill exits here.
CLI Reference
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.
- 9d ago First seen · 107 lines · 12 tokens per session scan A a674bf0a6613
review is a skill published in the GitHub repository happy-nut/claude-plugin-viban (5 stars, last pushed 6mo ago), licensed MIT. It adds 12 tokens to every session and 623 once invoked, about $0.0001 per session on Opus 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
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
verify-behavior
Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…
github-contributor
End-to-end playbook for shipping high-quality pull requests to open-source projects you don't maintain — discovery, CONTRIBUTING compliance, PR-size check, minimal-diff implementation, PR description with AI-assisted disclosure, conflict resolution, and post-submission maintainer interaction. Use whenever creating…
revdiff
Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…
write-pr
Reference standards for writing pull request titles and descriptions in the tldraw repository, plus the pre-flight comment sweep over the diff. Use as supporting guidance when another skill or workflow needs PR content standards, not as the user-facing create/update PR workflow.