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 rejectgit 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/reject)<a href="https://agentmods.dev/skills/happy-nut/claude-plugin-viban/reject"><img src="https://agentmods.dev/badge/skills/happy-nut/claude-plugin-viban/reject.svg" alt="Measured on agentmods" 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.00013 | $0.00662 |
| Opus 5 | $0.00006 | $0.00331 |
| Sonnet 5 | $0.00003 | $0.00132 |
| Haiku 4.5 | $0.00001 | $0.00066 |
Grade A, and why
reject 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 8d 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/reject
Reject a review-status issue and move it back to in_progress. The worktree stays intact so the agent can address feedback.
CLI only (no direct viban.json access)
Input: $ARGUMENTS (required: issue ID, optional: feedback text)
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.
Parse $ARGUMENTS: first token is $ID, rest is $FEEDBACK.
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: Re-attach Worktree
If worktree exists (detached during review), re-attach it to the branch:
[ -d "$WT_DIR" ] && git -C "$WT_DIR" checkout "$BRANCH"
If worktree does not exist, recreate it:
[ ! -d "$WT_DIR" ] && git worktree add "$WT_DIR" "$BRANCH"
Step 4: Move Back to in_progress
viban move $ID in_progress
Step 5: Record Feedback
If $FEEDBACK is provided:
viban comment $ID "$FEEDBACK"
Also comment on PR if one exists:
PR_NUM=$(gh pr list --head "$BRANCH" --json number --jq '.[0].number' 2>/dev/null)
[ -n "$PR_NUM" ] && gh pr comment "$PR_NUM" --body "$FEEDBACK"
If no feedback provided, ask the user: "Any feedback for the developer?"
- If provided → store as comment
- If none → skip
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 rejected → in_progress. Worktree intact at $WT_DIR."
CLI Reference
| Command | Description |
|---|---|
viban get <id> |
View issue details |
viban move <id> <status> |
Move issue to status |
viban comment <id> "<text>" |
Add comment to issue |
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.
- 8d ago First seen · 120 lines · 13 tokens per session scan A 6b7844cb14a6
reject is a skill published in the GitHub repository happy-nut/claude-plugin-viban (5 stars, last pushed 6mo ago), licensed MIT. It adds 13 tokens to every session and 662 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.