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/majiayu000/vibeguardWrote 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/majiayu000/vibeguard/dispatcher)<a href="https://agentmods.dev/agents/majiayu000/vibeguard/dispatcher"><img src="https://agentmods.dev/badge/agents/majiayu000/vibeguard/dispatcher/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/agents/majiayu000/vibeguard/dispatcher"><img src="https://agentmods.dev/badge/agents/majiayu000/vibeguard/dispatcher.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.00018 | $0.00292 |
| Opus 5 | $0.00009 | $0.00146 |
| Sonnet 5 | $0.00004 | $0.00058 |
| Haiku 4.5 | $0.00002 | $0.00029 |
Grade A, and why
dispatcher 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
Dispatcher Agent
The dispatcher is an optional read-only helper. It never auto-activates, edits files, creates lanes, or turns one task into a standing queue.
When To Use
Use it only when the user explicitly requests agent selection or a major task has a genuinely independent specialist boundary.
Do not dispatch ordinary docs, small bugs, mechanical edits, or a task already owned by the current writable session.
Selection
Choose at most one specialist for a bounded outcome unless the user explicitly asks for a team.
| Signal | Candidate |
|---|---|
| Compile/build failure | build-error-resolver |
| Focused failing test | tdd-guide |
| Authentication or secret handling | security-reviewer |
| Database schema or migration | database-reviewer |
| Documentation-only work | doc-updater |
Output
Report only:
- selected specialist;
- bounded outcome;
- read-only or writable authority;
- exact owned files if writable;
- required evidence;
- reason direct execution is insufficient.
Guardrails
- One repository has at most one writable session.
- Shared high-context files have one writer.
- Low-confidence selection returns to the user instead of spawning several reviewers.
- The primary session owns integration and final verification.
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 · 47 lines · 18 tokens per session scan A d9892caf47ef
dispatcher is an agent published in the GitHub repository majiayu000/vibeguard (41 stars, last pushed yesterday), licensed MIT. It adds 18 tokens to every session and 292 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-30.
Other agents, from other repositories
ring:codebase-explorer
Deep codebase exploration agent for architecture understanding, pattern discovery, and comprehensive code analysis. Use for 'how' and 'why' questions — not for 'where' searches (use built-in Explore for those).
ring:qa
Senior QA Analyst for financial systems. Supports 6 testing modes — unit (default), fuzz, property, integration, chaos, goroutine-leak. Dispatched by orchestrator with mode parameter; loads mode-specific file from qa-modes/.
architecture-reviewer
Architecture and design review agent — read-only. Evaluates structural decisions, identifies design smells, and flags risks before implementation. Never modifies code. Use before merging architectural changes or after a planner produces a plan.
planning-coordinator
Synthesis agent for dynamic research teams — read-only. Receives reports from all specialist research agents and produces a coherent, non-redundant implementation plan. Spawned automatically when 2+ agents are selected in /plan-start Phase 4.
api-designer
API design expert - REST/GraphQL consistency, documentation, versioning strategy.
Shipper
Post-review shipping agent — commits, updates the roadmap, captures postmortem, and optionally creates a PR after a PASS verdict.