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 xiaotianfotos/homerail --skill homerail-pr-closeoutgit clone --depth 1 https://github.com/xiaotianfotos/homerailWrote 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/xiaotianfotos/homerail/homerail-pr-closeout)<a href="https://agentmods.dev/skills/xiaotianfotos/homerail/homerail-pr-closeout"><img src="https://agentmods.dev/badge/skills/xiaotianfotos/homerail/homerail-pr-closeout/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/xiaotianfotos/homerail/homerail-pr-closeout"><img src="https://agentmods.dev/badge/skills/xiaotianfotos/homerail/homerail-pr-closeout.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00048 | $0.00416 |
| Opus 5 | $0.00024 | $0.00208 |
| Sonnet 5 | $0.00010 | $0.00083 |
| Haiku 4.5 | $0.00005 | $0.00042 |
Grade A, and why
homerail-pr-closeout 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
`create_and_run`, shell, `gh`, or `curl` to reconstruct the snapshot. The What it actually says
HomeRail PR Closeout
Use the concrete pr-closeout orchestration after implementation and local
validation are complete. Do not substitute a conversational checklist.
Safety Boundary
- Never call a GitHub merge API or
gh pr merge. - Never represent HomeRail approval as a GitHub approval or merge.
- Never accept validation evidence whose head differs from the current PR head.
- Never let a model override deterministic blockers.
Draft Closeout
For a Draft PR, use one of these paths:
- Call
run_pr_closeoutwithrepo, integerpr,phase: draft, and durablevalidation_runs. Do not invent run ids. - Run
hr dag run-template pr-closeoutwith explicit operator-attested local evidence bound to a commit SHA.
A successful result means only ready_for_review; the PR must still run normal
GitHub CI and PR Review after leaving Draft.
Merge Closeout
For a non-Draft PR, call run_pr_closeout with durable validation_runs,
especially the matching HomeRail PR Review run. Do not use generic
create_and_run, shell, gh, or curl to reconstruct the snapshot. The
workflow may pause at merge_approval. Return the real run id and the exact
blocker list or pending approval hash. Only human:owner may decide that
approval, and the user still merges manually.
After a terminal decision, consume the declared pr-closeout.json artifact
with hr dag artifact <run-id> pr-closeout.json --output pr-closeout.json.
Never reconstruct closeout evidence by scraping handoffs.
Read docs/scenarios/pr-closeout.md for the full evidence contract.
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 · 47 lines · 48 tokens per session scan A fafa08cbe6a3
homerail-pr-closeout is a skill published in the GitHub repository xiaotianfotos/homerail (951 stars, last pushed today), licensed MIT. It adds 48 tokens to every session and 416 once invoked, about $0.0002 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-30.
Other skills, from other repositories
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
verify-behavior
Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…
github-contributor
End-to-end playbook for shipping high-quality pull requests to open-source projects you don't maintain — discovery, CONTRIBUTING compliance, PR-size check, minimal-diff implementation, PR description with AI-assisted disclosure, conflict resolution, and post-submission maintainer interaction. Use whenever creating…
revdiff
Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…
oss-maintainer
Run an open-source project's issue/PR/release loop like a careful human maintainer — triage to root cause, absorb community PRs before duplicating them, gate every merge, ship honest releases, and thank the people doing your QA for free.