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/DmitriyYukhanov/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/plugins/dmitriyyukhanov/claude-plugins/agent-dispatch)<a href="https://agentmods.dev/plugins/dmitriyyukhanov/claude-plugins/agent-dispatch"><img src="https://agentmods.dev/badge/plugins/dmitriyyukhanov/claude-plugins/agent-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/dmitriyyukhanov/claude-plugins/agent-dispatch"><img src="https://agentmods.dev/badge/plugins/dmitriyyukhanov/claude-plugins/agent-dispatch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
agent-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 5d 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": "agent-dispatch",
"version": "1.3.2",
"description": "Start issue-to-pr runs from GitHub labels on your own machine: a scheduled tick picks the issue you labelled agent, or the one you replied on, and runs it headless under your own Claude Code or Codex login, on Windows, macOS or Linux.",
"author": {
"name": "Dmitry Yuhanov"
},
"dependencies": [
{ "name": "issue-to-pr" }
]
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 85 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.
- 5d ago Changed f57ea69343ad
- 6d ago Changed 0d2982069115
- 12d ago Changed 7706e8c63856
- 15d ago First seen · 12 lines scan A 600f4f8172ba
agent-dispatch is a plugin published in the GitHub repository DmitriyYukhanov/claude-plugins (8 stars, last pushed 2d ago), 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-09-29.
Other plugins, from other repositories
dark-factory
Curie's default dark factory agent: one labelled GitHub issue in, one reviewed pull request or one stated reason out. One agent reads the issue through the platform's getissue tool, pins acceptance criteria, plans, gets the plan reviewed by an Opus plan-reviewer subagent, writes a failing test where feasible, implemen.
github
GitHub CLI, stacked PRs, Actions docs, and issue management skills.
release-conductor
Owns everything around the diff: craft Conventional Commits and PR descriptions, recommend the right semver bump by reasoning about behavioral breaking changes, assemble changelogs from messy history, and guide merge-conflict resolution, rebase planning, and git-history archaeology.
branch-recap
Tells you what your branch actually changed — what was done, why, and what deserves a second look, instead of the diff — then files the fixes into the commits they belong to.
slack-changelog
Turns what changed in a release into a Slack changelog a non-technical audience can read — filtered to what they'd notice, one theme, one bullet per idea, no code vocabulary.
telegram-topics
Telegram channel for Claude Code — 1 project = 1 forum topic, with a live working/idle status badge on each topic. Run multiple projects concurrently, get notifications, and drive or approve sessions remotely from your phone. Configure with /telegram-topics:configure.