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.
npx skills add emaraschio/cursor-commands --skill merge-open-prsgit clone --depth 1 https://github.com/emaraschio/cursor-commandsWrote 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/skills/emaraschio/cursor-commands/merge-open-prs)<a href="https://agentmods.dev/skills/emaraschio/cursor-commands/merge-open-prs"><img src="https://agentmods.dev/badge/skills/emaraschio/cursor-commands/merge-open-prs/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/skills/emaraschio/cursor-commands/merge-open-prs"><img src="https://agentmods.dev/badge/skills/emaraschio/cursor-commands/merge-open-prs.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.00065 | $0.02197 |
| Opus 5.5 | $0.00026 | $0.00879 |
| Sonnet 5.5 | $0.00013 | $0.00439 |
| Haiku 4.5 | $0.00006 | $0.00220 |
Grade A, and why
merge-open-prs 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.
How it starts
The opening of the file, as written. The whole thing — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Merge open PRs
Orchestrate a batch of open pull requests in the current repo: babysit each PR, code-review, verify locally (Docker-first), auto-merge when green, then post-batch smoke on the default branch.
Do not duplicate the babysit contract inline. Read and follow the babysit skill at ~/.cursor/skills-cursor/babysit/SKILL.md for every PR in the batch.
Entry point: .cursor/commands/merge-open-prs.md (slash /merge-open-prs). When this file disagrees with the command file, this file wins.
Defaults
Apply these when the user does not override:
| Setting | Default | Override |
|---|---|---|
| Verification | Docker-first | --no-docker |
| Batch size | 10 PRs | --limit N |
| Autonomy | auto_if_green (merge when gate passes) | --dry-run (no merge) |
| Single PR | Process only that number | 42 or #42 argument |
Parse flags from the user message: --dry-run, --no-docker, --limit N. A bare number selects one PR.
When NOT to use
- Single PR babysit only (no batch, no queue) → use babysit on that PR directly
- Cross-repo initiative status → use cross-repo-status or manual
ghsweep per user rules - PRs needing product/legal sign-off → skip; report in summary
- Sensitive security changes without explicit user approval → hard stop
- Repo has no Docker and user did not pass
--no-docker→ blocker at preflight (do not silently fall back)
Phase 0: Preflight
gh auth status: blocker if not authenticated- Confirm git repo root:
git remote get-url origin git fetch --all --prune- If working tree dirty → warn; do not stash without asking
- Docker (default path):
docker info. If it fails and user did not pass--no-docker, stop with a blocker (suggest--no-dockeronly when they accept non-Docker verification) - Resolve profile path:
profiles/<repo-basename>.yamlrelative to this skill directory (basenamefromgit remote get-url origin, strip.git, last path segment). Seeprofiles/README.md.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 217 lines · 65 tokens per session scan A 18e13b90165e
merge-open-prs is a skill published in the GitHub repository emaraschio/cursor-commands (9 stars, last pushed 3d ago), licensed MIT. It adds 65 tokens to every session and 2,197 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
active-review
Use when the user wants to prepare for a manual PR code review and asks for help targeting it — a terse PR summary, ranked files to read first, and paste-ready inline comment drafts with GitHub deep-links. Triggers: "active review this PR", "walk me through this PR", "help me review this", "give me inline comments to…
pr-requirement-capture
Use when GH starts a message with "PR :" or "PR:". Treat the following text as a requirement that should be captured and worked through a GitHub pull-request workflow instead of remaining only in chat.
gentle-ai-collab-perfect
Trigger: contributing to Gentleman-Programming/gentle-ai as an external collaborator. Strict issue-first workflow, honest PR bodies, contributor-vs-maintainer scope, chained-PR strategy, verification protocol, docstring coverage. Load whenever the active repo is Gentleman-Programming/gentle-ai and any part of the…
branch-pr
Create Gentle AI pull requests with issue-first checks. Trigger: creating, opening, or preparing PRs for review.
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.
work-with-pr
Full PR lifecycle in a fresh task-owned git worktree: implement via the ulw-loop skill with mandatory evidence-bound manual QA → reviewer-readable English PR → verification loop (CI + Cubic, where Cubic is skipped only when its quota is exhausted) → merge by default → worktree cleanup. Decomposes one task into the…