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/rules/forward-future/deploybot/manage-merge-queue)<a href="https://agentmods.dev/rules/forward-future/deploybot/manage-merge-queue"><img src="https://agentmods.dev/badge/rules/forward-future/deploybot/manage-merge-queue/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/rules/forward-future/deploybot/manage-merge-queue"><img src="https://agentmods.dev/badge/rules/forward-future/deploybot/manage-merge-queue.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.00212 | $0.00212 |
| Opus 5.5 | $0.00085 | $0.00085 |
| Sonnet 5.5 | $0.00042 | $0.00042 |
| Haiku 4.5 | $0.00021 | $0.00021 |
Grade A, and why
manage-merge-queue 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
Read .mergequeue.toml and use the deploybot MCP tools. Keep changing
PRs draft and make the final ready head immutable. Address valid feedback from
whatever review providers the repository configures.
Only the user's exact deploy instruction authorizes request_deployment for
the current thread's PR. Include the stable Cursor thread ID. Durable intent
wakes GitHub and promotes only after fresh exact-head gates; never poll or merge
an unlabeled PR. Use pipeline_status and react_to_delivery_event, skip
blockers, honor dependencies, route overlaps or cumulative validation through
one integration PR, return repair packets to their source thread, atomically
resume after fresh review, and follow cumulative main through deployment. In
release_admission = "merged" mode, admit independent ready work immediately
after merge while later events continue release tracking.
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 · 19 lines · 212 tokens per session scan A 20f56e770a0f
manage-merge-queue is a cursor rule published in the GitHub repository Forward-Future/DeployBot (44 stars, last pushed 3mo ago), licensed MIT. It adds 212 tokens to every session, about $0.0008 per session on Opus 5.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 cursor rules, from other repositories
pr-policy
Repository-wide pull request contract for every Cursor agent.
agents-shipgate
Run Agents Shipgate as the deterministic merge gate for AI-generated agent capability changes.
handoff
Export a Waybill Bundle by default, or import one when explicitly requested.
repo-context
Read AGENTS.md first. Treat it as the source of truth for this repo's commands, invariants, public naming, release constraints, and first-user path.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.