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 agentmods add skills/urmzd/dotfiles/merge-readynpx 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.svg" alt="Measured on agentmods" 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 | $0.00104 | $0.01251 |
| Sonnet 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 5d 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.
- 5d ago First seen · 193 lines · 208 tokens per session scan A 12d86cf6c688
merge-ready is a skill published in the GitHub repository urmzd/dotfiles (3 stars, last pushed 23d ago), licensed Apache-2.0. It adds 208 tokens to every session and 2,502 once invoked, about $0.0010 per session on Opus 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
benchling-integration
Benchling Python SDK and REST API integration for registry entities, inventory, ELN entries, workflows, Benchling Apps, and Data Warehouse queries. Use when automating lab data with benchling-sdk or the v2 API.
astropy
Core Python library for astronomy and astrophysics workflows that need Astropy APIs, including units/quantities, coordinates, FITS I/O, tables, time systems, WCS, and cosmology. Use when implementing or debugging astronomical data analysis code with Astropy.
esm
Comprehensive toolkit for EvolutionaryScale protein language models including ESM3 (generative multimodal design across sequence, structure, and function) and ESM C (efficient embeddings). Use for protein sequence/structure/function tasks, inverse folding, embeddings, variant design, and ESMFold2 structure prediction…
ralph-loop
Ralph Wiggum 迭代开发循环。三阶段工作流(需求→规划→构建),每阶段有 code review + 测试 gate。 触发词:ralph loop、迭代开发、interview me、plan system、build system。.
mcp-notion-usage-guide
MCP Notion工具使用指南,包含常见问题解决方案和最佳实践。使用当: (1) 访问Notion数据库view URL出现"URL type view not currently supported"错误, (2) 需要获取数据库schema和表结构信息, (3) 查询数据库中的条目内容, (4) 创建页面时MULTISELECT字段值不存在导致失败, (5) 需要更新数据库schema添加新选项, (6) 开发需要集成Notion数据的自动化工作流, (7) querydatasources/query-database-view返回Business Plan要求错误, (8) 需要在无Business…
scan-commit
Automatically scan the repository for unstaged/untracked changes, group them into logical commits using hunk-level analysis, stage and commit them following Conventional Commits.