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.
git clone --depth 1 https://github.com/shrwnsan/vibekit-claude-pluginsWrote 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/agents/shrwnsan/vibekit-claude-plugins/workflow-orchestrator)<a href="https://agentmods.dev/agents/shrwnsan/vibekit-claude-plugins/workflow-orchestrator"><img src="https://agentmods.dev/badge/agents/shrwnsan/vibekit-claude-plugins/workflow-orchestrator.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.00024 | $0.01055 |
| Opus 5 | $0.00012 | $0.00528 |
| Sonnet 5 | $0.00005 | $0.00211 |
| Haiku 4.5 | $0.00002 | $0.00105 |
Grade A, and why
workflow-orchestrator 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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 · 133 lines · 24 tokens per session scan A adfe4fc0a3a2
workflow-orchestrator is an agent published in the GitHub repository shrwnsan/vibekit-claude-plugins (7 stars, last pushed 18d ago), with no licence file. It adds 24 tokens to every session and 1,055 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 agents, from other repositories
parallel-integrate
Integrate parallel workflow branches. Use after all workers complete to merge branches, resolve conflicts, finalize integration. Triggers: integrate, merge workers, combine branches, finish parallel.
parallel-setup
Set up parallel workflow with git worktrees. Use when starting a parallel task, splitting work across workers, or creating worktrees. Triggers: parallel setup, create worktrees, split work, prepare workers.
parallel-monitor
Monitor parallel workflow progress. Use to check worker status, detect stalls, find blocked workers. Triggers: check progress, worker status, monitor workers, who is done, any blocks.
git-assistant
Use this agent for complex git operations like rebasing, cherry-picking, resolving merge conflicts, bisecting, and history cleanup. Examples: User: "Resolve the merge conflict" Assistant: "I'll launch the git-assistant agent to analyze and resolve the conflict." User: "Clean up my branch history" Assistant: "Let me…
pr-analyzer
Use this agent to analyze GitHub PRs -- check CI status, read review comments, assess merge readiness, and suggest next actions. Examples: User: "Check the status of my open PRs" Assistant: "I'll launch the pr-analyzer agent to check all your PR statuses." User: "Why is CI failing on my PR?" Assistant: "Let me launch…
repo-auditor
Use this agent to audit a repository for hygiene issues -- missing README, LICENSE, .gitignore, .env.example, stale branches, and configuration problems. Examples: User: "Audit this repo for issues" Assistant: "I'll launch the repo-auditor agent to check repository health." User: "Is this repo properly set up?"…