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 parallel-assigngit 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/parallel-assign)<a href="https://agentmods.dev/skills/happy-nut/claude-plugin-viban/parallel-assign"><img src="https://agentmods.dev/badge/skills/happy-nut/claude-plugin-viban/parallel-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.00020 | $0.02285 |
| Opus 5 | $0.00010 | $0.01143 |
| Sonnet 5 | $0.00004 | $0.00457 |
| Haiku 4.5 | $0.00002 | $0.00229 |
Grade A, and why
parallel-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 7d 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 — 303 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/parallel-assign
Parallel resolution of independent backlog issues via git worktrees.
CLI only (no direct viban.json access) | Opus sub-agents in isolated worktrees
vibanis a zsh CLI tool. Always invoke asviban <command>, NEVER aspython -m vibanorpython viban.
Input: $ARGUMENTS (optional: number of issues, default 3)
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. Each agent must complete its assigned issue fully — 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 Phase 0 immediately and silently.
Phase 0: SETUP
0.1 Read Workflow
[ -f ".viban/workflow.md" ] && cat ".viban/workflow.md"
Fallback to CLAUDE.md, then default. Same as /viban:assign Phase 0.1.
0.2 Parse Arguments
Extract count from $ARGUMENTS:
- Number provided (e.g.
/viban:parallel-assign 5) → use that number - No number → default to 3
- Maximum: 5
0.3 Check Backlog & Git State
viban list
Count available backlog issues. Adjust N down if fewer available. If backlog is empty: notify user and exit.
[ -n "$(git status --porcelain)" ] && echo "Warning: Uncommitted changes"
git checkout main && git fetch origin main && git reset --hard origin/main
0.4 Assign Issues
Assign N issues, each with a unique session ID. Determine branch names per workflow convention:
ISSUES=() # Array of "ID|BRANCH" pairs
for i in $(seq 1 $N); do
SESSION=$(echo "${RANDOM}${i}" | md5 | head -c 8)
ID=$(viban assign "$SESSION" 2>&1 | tail -1)
[[ -z "$ID" || "$ID" == "No backlog" ]] && break
BRANCH="issue-${ID}"
ISSUES+=("${ID}|${BRANCH}")
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.
- 7d ago First seen · 303 lines · 20 tokens per session scan A d4e63890ec25
parallel-assign is a skill published in the GitHub repository happy-nut/claude-plugin-viban (5 stars, last pushed 6mo ago), licensed MIT. It adds 20 tokens to every session and 2,285 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-sync-helper
General GitHub basic operations + automation for GitHub platform objects (Issues/Labels/Milestones/Releases/Actions) in the Minis environment. This skill must be triggered when the user mentions any basic Git/GitHub operation or workflow, including "how to use GitHub," clone, init, remote, branch, commit, push, pull…