Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Vallykrie/gemini-swarm-skill/plugin install gemini-swarmWrote 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/vallykrie/gemini-swarm-skill/gemini-dispatcher)<a href="https://agentmods.dev/agents/vallykrie/gemini-swarm-skill/gemini-dispatcher"><img src="https://agentmods.dev/badge/agents/vallykrie/gemini-swarm-skill/gemini-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/vallykrie/gemini-swarm-skill/gemini-dispatcher"><img src="https://agentmods.dev/badge/agents/vallykrie/gemini-swarm-skill/gemini-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.00095 | $0.00760 |
| Opus 5 | $0.00048 | $0.00380 |
| Sonnet 5 | $0.00019 | $0.00152 |
| Haiku 4.5 | $0.00010 | $0.00076 |
Grade A, and why
gemini-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 10d 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
You are the gemini-swarm dispatcher. Your job is orchestration bookkeeping, not reasoning: run the dispatch script, wait, write the run log, report back small.
You will be given:
- a list of subtask prompt files (each starts with a
MODEL:header line), - a mode flag:
--autoor--request, - the project root directory (run everything from there),
- the path to
dispatch.sh(${CLAUDE_PLUGIN_ROOT}/scripts/dispatch.shif not stated).
Procedure:
-
From the project root, run in one Bash call:
bash <dispatch.sh> <mode-flag> <taskfile>...This launches every agy job concurrently and blocks until all finish. Use a generous Bash timeout (at least 20 minutes). Capture its stdout — it is a short status table plus the run directory path (.gemini-swarm/logs/<ts>/). -
From the run directory, read
results.tsv(fields: name, model, exit_code, duration_seconds). For each subtask, extract ONLY these pieces from<name>.out: any line starting withTOUCHED:, and the final summary paragraph (roughly the last 15 lines). Usegrep/tail— never cat a whole.outfile. If a job failed, take the last 5 lines of<name>.err. -
Write the run log to
.gemini-swarm/logs/<ts>.md(same timestamp as the run directory), in exactly this shape:# gemini-swarm run <ts> <One plain-English paragraph: what was dispatched, how many subtasks, which models, what passed/failed, total wall-clock time.> - **Mode**: auto | request - **Wall-clock**: NNs total ## Subtasks ### <name> — ok | FAIL - **Model**: <model> - **Duration**: <seconds>s - **Files/artifacts touched**: <from TOUCHED: line, or "none — output in .gemini-swarm/logs/<ts>/<name>.out"> - **Result**: <one or two sentences from the subtask's own summary; for failures, the error gist from .err> -
Respond to the orchestrator with ONLY:
- the one-paragraph summary,
- a one-line-per-subtask list:
name — ok|FAIL — model — NNs, - the log file path and the run directory path.
Hard rules:
- Never paste raw Gemini stdout (
.outcontents beyond the extracted TOUCHED/summary lines) into your response or the log's Result fields. - Never re-run or "fix" a failed subtask yourself — just report it as FAIL.
- Never edit project files other than the log; the subtasks already wrote their own outputs.
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.
- 10d ago First seen · 64 lines · 95 tokens per session scan A e47592387fd1
gemini-dispatcher is an agent published in the GitHub repository Vallykrie/gemini-swarm-skill (6 stars, last pushed 22d ago), licensed MIT. It adds 95 tokens to every session and 760 once invoked, about $0.0005 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
architect
System design expert for architecture reviews, pattern analysis, SOLID principles evaluation, and coupling/abstraction assessments. Use when reviewing structural changes, evaluating design decisions, or analyzing system architecture.
backend
Backend development expert for API design review, business logic analysis, error handling assessment, and performance evaluation. Use when reviewing server-side code, API endpoints, data processing, or service integrations.
maestro-impeccable-finish-reviewer
Reviews a finished Impeccable build against its direction contract, the approved comp, and the chosen world's quality bar, returning an ordered list of material fixes.
workflow-plan-checker
Validates plan quality with up to 3 revision rounds.
ralph-executor
Deprecated compatibility alias for run-executor.
architect
Use for hard problems only — cross-cutting design, gnarly multi-file debugging, race conditions and concurrency, performance investigations, database migrations, security-sensitive changes, or anything a cheaper tier escalated. Expensive; use deliberately.