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 skyfox675/agents-skills --skill driving-prs-to-mergegit clone --depth 1 https://github.com/skyfox675/agents-skillsWrote 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/skyfox675/agents-skills/driving-prs-to-merge)<a href="https://agentmods.dev/skills/skyfox675/agents-skills/driving-prs-to-merge"><img src="https://agentmods.dev/badge/skills/skyfox675/agents-skills/driving-prs-to-merge/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/skyfox675/agents-skills/driving-prs-to-merge"><img src="https://agentmods.dev/badge/skills/skyfox675/agents-skills/driving-prs-to-merge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 191 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00191 | $0.06458 |
| Opus 5 | $0.00096 | $0.03229 |
| Sonnet 5 | $0.00038 | $0.01292 |
| Haiku 4.5 | $0.00019 | $0.00646 |
Grade A, and why
driving-prs-to-merge 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 12d 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 — 271 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Driving PRs to Merge
After opening any PR, the opener owns driving it to merge. No waiting for a human nudge. The loop exit condition: all required checks green AND every review thread resolved — auto-merge then fires on its own. Everything below exists to get to that state cheaply and honestly.
Project bindings
This skill is project-agnostic. The adopting project defines these in its own CLAUDE.md; refer to them by placeholder throughout.
| Placeholder | Meaning |
|---|---|
<owner>/<repo> |
GitHub repository slug |
<integration-branch> |
Branch PRs target (may differ from the repo default branch — see "After merge") |
<merge-strategy> |
Allowed strategy flag (--squash, --merge, --rebase) — and whether a merge queue is enabled (changes the command, see below) |
<local-gate> |
The full local verification command CI will mirror (lint + typecheck + tests), ideally scoped to changed packages + dependents |
<worktree-dir> |
Where feature branches live on disk (see the dispatching-subagents skill) |
<bot-reviewer> |
AI review bot identity (if any), whether it reviews sync or async, and whether the ruleset enables required_review_thread_resolution |
<required-checks> |
Names of merge-gating CI checks |
<failure-catalog> |
Location of the failure-pattern catalog (maps check-name → likely cause → fix recipe → evidence PR#) |
<flake-ledger> |
Where known-flaky jobs are tracked (e.g. a scheduled workflow posting to a pinned issue); absent → degrade to "retry twice on same SHA" |
<per-pr-deploy> |
Per-PR preview-environment workflow, if any, and its path filter |
<breaking-change-labels> |
Acknowledgment labels/annotations that breaking-change gates honor |
<derived-artifacts> |
Generated files (lockfiles, operation manifests) + their regeneration commands |
<append-only-files> |
Shared append-only files (changelogs, learnings logs) that conflict trivially |
<ai-mention-trigger> |
The human-only AI-action mention string (e.g. @claude), if the repo has one |
<force-push-policy> |
Who may force-push feature branches (some environments permission-block sub-agents; orchestrator performs with operator authorization) |
<commit-convention> |
Commit message format; see the dispatching-subagents skill for the canonical definition |
What ships with it
1 file 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.
- 12d ago First seen · 271 lines · 191 tokens per session scan A bf43e771f238
driving-prs-to-merge is a skill published in the GitHub repository skyfox675/agents-skills (11 stars, last pushed 12d ago), licensed MIT. It adds 191 tokens to every session and 6,458 once invoked, about $0.0010 per session on Opus 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-31.
Other skills, from other repositories
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
deployment-patterns
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.
baby-sit
Monitor a GitHub pull request until CI is green, diagnose failures, and rerun only evidence-backed flaky GitHub Actions jobs.
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
atmos-hooks
Atmos hooks: lifecycle events, hook kinds, command/store/git/security hooks, step/steps hooks, when: conditions, scoping and overrides, toolchain integration, --skip-hooks, and Atmos Pro/local output.