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/bendrucker/claudeWrote 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/plugins/bendrucker/claude/dispatch)<a href="https://agentmods.dev/plugins/bendrucker/claude/dispatch"><img src="https://agentmods.dev/badge/plugins/bendrucker/claude/dispatch/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/plugins/bendrucker/claude/dispatch"><img src="https://agentmods.dev/badge/plugins/bendrucker/claude/dispatch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
dispatch 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 11d 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
{
"name": "dispatch",
"description": "Hand new work to a fresh Claude session in its own worktree, in a Rex tab or a herdr workspace",
"author": {
"name": "Ben Drucker",
"email": "[email protected]"
}
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 92 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 11d ago First seen · 9 lines scan A 8440dc332996
dispatch is a plugin published in the GitHub repository bendrucker/claude (18 stars, last pushed today), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-10-30.
dispatch compared with plugins from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| dispatchbendrucker/claude | Plugin | 18 | today | MIT | A | — | Claude Code |
| han-githubtestdouble/han | Plugin | 342 | 8d ago | MIT | A | — | Claude Code |
| dark-factorycurie-eng/curie | Plugin | 48 | today | Apache-2.0 | A | — | Claude Code |
| github-activitycurie-eng/curie | Plugin | 48 | today | Apache-2.0 | A | — | Claude Code |
| git-commitxobotyi/cc-foundry | Plugin | 23 | yesterday | MIT | A | — | Claude Code |
| fuse-commit-profusengine/agents | Plugin | 34 | 28d ago | MIT | A | — | Claude Code |
| core-guardsfusengine/agents | Plugin | 34 | 28d ago | MIT | A | — | Claude Code |