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 LucasSantana-Dev/sharekit --skill pr-merge-readinessgit clone --depth 1 https://github.com/LucasSantana-Dev/sharekitWrote 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/lucassantana-dev/sharekit/pr-merge-readiness)<a href="https://agentmods.dev/skills/lucassantana-dev/sharekit/pr-merge-readiness"><img src="https://agentmods.dev/badge/skills/lucassantana-dev/sharekit/pr-merge-readiness/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/lucassantana-dev/sharekit/pr-merge-readiness"><img src="https://agentmods.dev/badge/skills/lucassantana-dev/sharekit/pr-merge-readiness.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.00078 | $0.02499 |
| Opus 5 | $0.00039 | $0.01249 |
| Sonnet 5 | $0.00016 | $0.00500 |
| Haiku 4.5 | $0.00008 | $0.00250 |
Grade A, and why
pr-merge-readiness 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 9d 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 — 259 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Merge Readiness
Replaces the manual checklist of "is CI green? are reviews approved? does it conflict? did Sonar/CodeRabbit/Greptile finish? is the branch stale?" with a single skill that collects every signal and outputs one verdict.
Use When
- About to merge a PR and want one combined "ready / not ready" answer
- Reviewing many PRs in a batch and need a triage table
- Reviewing PRs from PR-Agent, CodeRabbit, or Greptile that already have third-party comments to reconcile
Do Not Use When
- The PR is still WIP and you know it isn't done — use
shiplater - Only one signal matters (e.g., just need CI status) — use
ci-watchdirectly - The work is on a branch with no PR yet — use
pr-flowto create one first
Inputs / Prereqs
ghCLI authenticated for the repo- PR number, URL, or current branch (defaults to current branch's open PR)
--strictflag: fail on any non-passing signal, even informational ones
Workflow
1. Identify the PR
# Default to current branch's PR
PR=$(gh pr view --json number -q .number 2>/dev/null)
[ -z "$PR" ] && { echo "No open PR for current branch"; exit 1; }
# Or use explicit arg
[ -n "$1" ] && PR="$1"
gh pr view "$PR" --json title,headRefName,baseRefName,mergeable,mergeStateStatus,\
isDraft,reviewDecision,statusCheckRollup,labels,additions,deletions,changedFiles,\
updatedAt,author,url
2. Collect signals
Run all checks in parallel where possible. Each produces a status: PASS, WARN, FAIL,
or SKIP (signal not applicable to this repo).
Signal 1: Draft state
gh pr view "$PR" --json isDraft -q .isDraft
Draft → FAIL (cannot merge a draft).
Signal 2: Mergeability and conflicts
gh pr view "$PR" --json mergeable,mergeStateStatus
mergeable: CONFLICTING → FAIL with the list of conflicting files.
mergeStateStatus: BLOCKED → FAIL (required reviews missing or branch protection).
mergeStateStatus: BEHIND → WARN (rebase/merge main needed).
mergeStateStatus: CLEAN → PASS.
What ships with it
3 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.
- 9d ago First seen · 259 lines · 78 tokens per session scan A 74dfbee01ae8
pr-merge-readiness is a skill published in the GitHub repository LucasSantana-Dev/sharekit (1 stars, last pushed 5d ago), licensed MIT. It adds 78 tokens to every session and 2,499 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
agentplane-task-closure-recovery
Use when Agentplane task completion, direct finish, branchpr integration, hosted-close, close-tail PRs, PR metadata, dirty task artifacts, or remote branch divergence need diagnosis or recovery.
argot-setup
Set argot up for a repository end to end — audit its history, decide what should shape its voice, fit, verify the fit actually catches things, tune the rules its own history says are noisy, and wire the places it runs (pre-write hook, pre-commit, MCP, CI). One sitting, one decision at a time, each proposed with the…
detect-task
Internal skill for commands. Detect the active task (any tracker adapter) from the task-state file / git branch name. Do not trigger on user conversation - only when commands need task detection.
dos-verify-done-claims
Before accepting an agent's 'done / shipped / fixed' claim, verify it against ground truth (git ancestry + the commit's own diff) using the DOS kernel's dos verify and dos commit-audit — never the agent's own narration.
take-task
A workflow for claiming a tracker task and preparing the development branch for it. It verifies the task, marks it as in progress, checks for uncommitted changes, and handles branch setup according to the task state.
session-boundary
Internal skill for commands. Resolve and VALIDATE this branch's session boundary - the ref a session's commit range is measured from - and report how much it can be trusted. Do not trigger on user conversation; only when a command needs the session range.