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 urmzd/dotfiles --skill merge-readygit clone --depth 1 https://github.com/urmzd/dotfilesWrote 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/urmzd/dotfiles/merge-ready)<a href="https://agentmods.dev/skills/urmzd/dotfiles/merge-ready"><img src="https://agentmods.dev/badge/skills/urmzd/dotfiles/merge-ready/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/urmzd/dotfiles/merge-ready"><img src="https://agentmods.dev/badge/skills/urmzd/dotfiles/merge-ready.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.00208 | $0.02502 |
| Opus 5.5 | $0.00083 | $0.01001 |
| Sonnet 5.5 | $0.00042 | $0.00500 |
| Haiku 4.5 | $0.00021 | $0.00250 |
Grade A, and why
merge-ready scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
`curl`, and list anything you cannot automate as a blocker in the report. How it starts
The opening of the file, as written. The whole thing — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Merge Ready
Take an open PR from wherever it is to "ready to merge", and report exactly what still needs a human when automation can't finish the job.
Steps
-
Detect the forge and pick the CLI: Read the remote (
git remote get-url origin) and choose the matching CLI, verifying it is installed and authenticated before proceeding:Host in remote URL CLI PR concept Auth check github.com / GHE ghpull request gh auth statusgitlab.com / self-hosted GitLab glabmerge request (MR) glab auth statusGitea / Forgejo / Codeberg teapull request tea login listThe steps below are written with
gh; on another forge, translate each operation to the equivalent verb (gh pr view->glab mr view --output json/tea pr <n>,gh pr comment->glab mr note,gh run view->glab ci view,gh pr update-branch->glab mr rebase, review threads ->glab api projects/:id/merge_requests/:iid/discussions). Confirm exact flags with--helprather than guessing. If the forge has no CLI (e.g. Bitbucket), fall back togitplus the forge's REST API viacurl, and list anything you cannot automate as a blocker in the report. -
Identify the PR: Resolve the argument (number or URL) or the current branch's PR via
gh pr view. If no PR exists, stop and suggest theprskill. If it is a draft, continue fixing but only mark it ready (gh pr ready) at the end, once everything else passes. -
Assess: Take one snapshot of the PR state:
gh pr view <n> --json number,title,body,url,state,isDraft,mergeable,mergeStateStatus,reviewDecision,reviewRequests,latestReviews,statusCheckRollup,baseRefName,headRefName,maintainerCanModify,closingIssuesReferencesThen fetch unresolved review threads (only GraphQL exposes resolution):
gh api graphql -f owner=<owner> -f repo=<repo> -F pr=<n> -f query=' query($owner:String!,$repo:String!,$pr:Int!){ repository(owner:$owner,name:$repo){ pullRequest(number:$pr){ reviewThreads(first:100){ nodes{ id isResolved isOutdated path line comments(first:20){ nodes{ author{login} body } } }} }} }'
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 · 193 lines · 208 tokens per session scan A 12d86cf6c688
merge-ready is a skill published in the GitHub repository urmzd/dotfiles (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 208 tokens to every session and 2,502 once invoked, about $0.0008 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
pr-review
Intelligent PR code review with dynamic agent allocation based on change types. Analyzes PR changes and generates targeted review tasks.
analyze-pr
Analyze a GitHub/GitLab Pull Request by fetching its diff, reading its web description, and generating a comprehensive document. Use when the user provides a PR link and wants to understand what changes the PR introduces, or asks to review/analyze/summarize a pull request.
review-code
Standalone code review for any scope — PR number, branch, file paths, or current changes. Synthesizes intent, runs 11 parallel specialized agents, and presents actionable findings with a verdict. For PR scope, optionally posts the review to GitHub with inline comments.
review-converge
Autonomously review and fix the current branch or specified scope in iterative rounds until clean, leaving all changes in the working tree. Escalates only genuine design decisions. Ends with a transparent report of every round, every fix, and anything it couldn't resolve.
review-prs
Fetch and present a prioritized summary of all PRs awaiting the current user's review across the relevant projects and provide an interactive workflow helping the user phrase and post inline review comments and overall review decisions.
review-pr-comments-converge
Fetch PR review comments, validate each against the actual code, auto-fix obvious issues, and escalate genuine design decisions. Leaves all changes in the working tree. Use when you want to action reviewer feedback autonomously.