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/Forward-Future/DeployBotWrote 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/forward-future/deploybot/claude-code)<a href="https://agentmods.dev/plugins/forward-future/deploybot/claude-code"><img src="https://agentmods.dev/badge/plugins/forward-future/deploybot/claude-code/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/forward-future/deploybot/claude-code"><img src="https://agentmods.dev/badge/plugins/forward-future/deploybot/claude-code.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
deploybot 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 1mo 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": "deploybot",
"version": "0.2.25",
"description": "DeployBot: a provider-neutral GitHub merge queue for coding agents",
"author": {
"name": "DeployBot contributors"
},
"license": "MIT"
}
What it installs
The manifest is a name and a version. 2 skills, 1 MCP server travel with it, and installing the plugin installs all of them — 111 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.
- 1mo ago First seen · 10 lines scan A 43ed39f733fb
deploybot is a plugin published in the GitHub repository Forward-Future/DeployBot (44 stars, last pushed 3mo 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-08-30.
Other plugins, from other repositories
hunch
A git-native reasoning graph of decisions, bugs, and invariants for your codebase — queried and enforced at reasoning time. Adds the hunch MCP tools plus /hunch:capture, /hunch:heal, /hunch:why, /hunch:fix, /hunch:fragile.
bellwether
Drive PRs to merge-ready: watch CI, fix failures, resolve review comments. Self-contained watch loop that keeps going until pr.ready=true.
ruflo-swarm
Agent teams, swarm coordination, Monitor streams, and worktree isolation — wraps 4 swarm + 8 agent MCP tools (12 total) plus 6 topologies (hierarchical / mesh / hierarchical-mesh / ring / star / adaptive).
beacon
Real-time presence and collision-avoidance for parallel AI coding agents. Warns you before two sessions edit the same file, or before a git checkout/reset/stash yanks the working tree out from under another agent.
sudocode
Git-native spec and issue management for AI-assisted development. Track issues, specs, and feedback with smart anchoring.
gh-watch
Watch GitHub pull requests and commits for CI status, reviews, comments, and merge conflicts.