Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/happy-nut/claude-plugin-vibannpx agentmods add skills/happy-nut/claude-plugin-viban/assignWrote 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/assign)<a href="https://agentmods.dev/skills/happy-nut/claude-plugin-viban/assign"><img src="https://agentmods.dev/badge/skills/happy-nut/claude-plugin-viban/assign.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.00012 | $0.01245 |
| Opus 5 | $0.00006 | $0.00622 |
| Sonnet 5 | $0.00002 | $0.00249 |
| Haiku 4.5 | $0.00001 | $0.00125 |
Grade A, and why
assign 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/assign
Assign the first backlog issue and execute the full resolution workflow. If the description is unclear, interview the user first.
CLI only (no direct viban.json access)
Output Rules
- Do NOT output any preamble. No "Your Task:", "I'll now...", "Let me...", or task summaries before starting work.
- NEVER delegate work back to the user. You must complete the entire issue yourself — writing code, tests, and verifying. Phrases like "Your Task:", "TODO(human)", "Waiting for your implementation", "Take your time", or any message that asks the user to write code are strictly FORBIDDEN. If you encounter a TODO comment, implement it yourself.
- Start executing Step 0 immediately and silently.
Step 0: Read Workflow (CRITICAL)
Check in priority order — first match wins:
.viban/workflow.md→[ -f ".viban/workflow.md" ] && cat ".viban/workflow.md"- CLAUDE.md (legacy, only if no workflow.md):
for path in "./CLAUDE.md" "./.claude/CLAUDE.md" "../CLAUDE.md"; do
[ -f "$path" ] && cat "$path"
done
Look for Issue Resolution Workflow or Workflow section.
If a workflow exists, follow it exactly — its pipeline, conventions, and stop points override the defaults below.
Step 1: Assign
ISSUE_ID=$(viban assign 2>&1 | tail -1)
[[ -z "$ISSUE_ID" || "$ISSUE_ID" == "No backlog" ]] && echo "No issues in backlog" && exit 0
If backlog is empty: notify user and exit.
Step 2: Read Issue
viban get $ISSUE_ID
Display the issue title, description, priority, and type to the user.
Step 3: Evaluate Clarity → Proceed Immediately
Assess whether the issue description provides enough context to start working.
- Clear → proceed directly to Step 4. Do NOT ask the user for confirmation. Do NOT ask "should I start?". Just start.
- Unclear → interview the user with AskUserQuestion to gather missing context, then proceed to Step 4 immediately.
Step 4: Locate Worktree
viban assign automatically creates a worktree. Locate it:
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 · 152 lines · 12 tokens per session scan A 4e12e9bb33cf
assign 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 1,245 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.