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 approvegit 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/approve)<a href="https://agentmods.dev/skills/happy-nut/claude-plugin-viban/approve"><img src="https://agentmods.dev/badge/skills/happy-nut/claude-plugin-viban/approve/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/approve"><img src="https://agentmods.dev/badge/skills/happy-nut/claude-plugin-viban/approve.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.00016 | $0.00573 |
| Opus 5 | $0.00008 | $0.00287 |
| Sonnet 5 | $0.00003 | $0.00115 |
| Haiku 4.5 | $0.00002 | $0.00057 |
Grade A, and why
approve 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.
What it actually says
/approve
Approve a review-status issue after IDE review. Merges the branch, removes the worktree, and marks the card done.
CLI only (no direct viban.json access)
Input: $ARGUMENTS (required: issue ID)
Output Rules
- Do NOT output any preamble.
- Start executing Step 1 immediately.
Step 1: Validate
viban get $ID
Confirm the issue is in review status. If not, tell the user and exit.
BRANCH="issue-$ID"
WT_DIR="$PWD/.viban/worktrees/$ID"
Step 2: Return to Main
Detached HEAD from /viban:review — branch is intact, just switch back:
git checkout main
Step 3: Merge
If PR exists
PR_NUM=$(gh pr list --head "$BRANCH" --json number --jq '.[0].number' 2>/dev/null)
If PR found:
gh pr merge "$PR_NUM" --squash --delete-branch
git pull origin main
If no PR (branch only)
git merge "$BRANCH" --no-ff -m "Merge issue-$ID: <title>"
git branch -d "$BRANCH"
If merge conflicts: help user resolve.
If no branch (main-direct work)
Nothing to merge. Proceed to Step 4.
Step 4: Cleanup Worktree
[ -d "$WT_DIR" ] && git worktree remove "$WT_DIR" --force 2>/dev/null
Step 5: Complete
viban done $ID
Step 6: Restore User State
Check for stash:
STASH=$(git stash list | grep "viban-review: before #$ID" | head -1 | cut -d: -f1)
[ -n "$STASH" ] && git stash pop "$STASH"
Check for temp commit:
TEMP=$(git log --oneline -1 | grep "viban-review: temp commit before #$ID")
[ -n "$TEMP" ] && git reset HEAD~1
Report: "Issue #$ID approved and merged."
CLI Reference
| Command | Description |
|---|---|
viban get <id> |
View issue details |
viban done <id> |
Mark issue as done |
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 · 118 lines · 16 tokens per session scan A 6c1d491144a7
approve is a skill published in the GitHub repository happy-nut/claude-plugin-viban (5 stars, last pushed 6mo ago), licensed MIT. It adds 16 tokens to every session and 573 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
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the stepfun-37 smoke test), open code review (ocr), PR…
cyrus-setup-repository
Add one or more Git repositories to Cyrus configuration so it can process issues from those repos.
github-sync
Bidirectional synchronization of epics and tasks with GitHub issues, labels, and relationships.
github-notification-triage
Triage GitHub notifications and issue/PR queues.