Borrowing it
Nothing to install: this file belongs to transloadit/node-sdk. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/transloadit/node-sdk/main/.ai/skills/gh-pr-to-green/SKILL.mdgit clone --depth 1 https://github.com/transloadit/node-sdkWrote 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/transloadit/node-sdk/gh-pr-to-green)<a href="https://agentmods.dev/skills/transloadit/node-sdk/gh-pr-to-green"><img src="https://agentmods.dev/badge/skills/transloadit/node-sdk/gh-pr-to-green/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/transloadit/node-sdk/gh-pr-to-green"><img src="https://agentmods.dev/badge/skills/transloadit/node-sdk/gh-pr-to-green.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.00065 | $0.00517 |
| Opus 5.5 | $0.00026 | $0.00207 |
| Sonnet 5.5 | $0.00013 | $0.00103 |
| Haiku 4.5 | $0.00006 | $0.00052 |
Grade A, and why
gh-pr-to-green 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 21d 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.
What it actually says
GH PR to Green
Workflow
- Get context from PR with
gh; make sure all review comments, threads, CI failures, and PR description updates are included, and track them as a todo list in your session (do not commit it). - Merge the latest main into our branch and resolve any conflict carefully.
- Determine which review items are correct.
- Keep working until all items are checked off, either by fixing the issue, or explaining why not in a PR comment or a code comment where applicable/sensible.
- Invoke
council-review - If the PR has UI/UX impact, invoke
claude-usertestinstead of duplicating browser-test instructions here. Treat its output as reviewer input, reconcile findings yourself, and fold valid fixes back into this PR-to-green loop. - Run the repo-required checks (often
yarn check). - Fix any issue that you deem related and worth fixing.
- Commit as you go, but push once per round: every push starts a full CI run, and in api2 a newer
push does not cancel the run for the commit it superseded. Cancel those superseded runs
(
gh run cancel). - Monitor CI until green with the repo's
gh-run-watch.tswhen it exists (api2:core/alphalib/bin/gh-run-watch.ts, content:_scripts/alphalib/bin/gh-run-watch.ts), elsegh run watch. - Fix any issue that you deem related and worth fixing, then push and watch again until CI is green or only 100% unrelated issues remain. Merge main again only for conflicts or a fix that main carries.
This skill is PR orchestration only. Do not add inline UX/browser/user-test instructions here; use dedicated validation skills for those workflows.
Report back with a list of all changes made, and offer a link to the PR for inspection and merge.
Offer to squash merge with --admin if the human thinks a last manual review is not needed.
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.
- 21d ago Changed · -17 tokens per session 0403eda096a8
- 2mo ago First seen · 42 lines · 82 tokens per session scan A d5f9ec368dd9
gh-pr-to-green is a skill published in the GitHub repository transloadit/node-sdk (73 stars, last pushed 2d ago), licensed MIT. It adds 65 tokens to every session and 517 once invoked, about $0.0003 per session on Opus 5.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-30.
Other skills, from other repositories
triage-contributor-pr
Triage open pull requests from external contributors to prisma/orm and produce a per-PR verdict with evidence. Use when a maintainer asks to triage, evaluate, assess, or review the queue of incoming contributor PRs, to decide whether a fork PR is safe to run CI on, to check whether a PR is in scope for its version…
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.
review-triage-phase
Produces canonical review actions from fetched review state and renders action markdown. Use when the user wants only triage/action-planning for the review-framework workflow.
compiler-commit
Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits with the [compiler] or [rust-compiler] prefix.
hero-diff-highlight
A dark code editor reveals a red deletion then a green addition with a soft pulse. Function: PR / code-change explainer.
reviewing-personhog-protocol
The full review process for personhog coordination-protocol changes — leases, fencing, handoffs, supervisors, failure budgets, warming, and changelog semantics. Use before pushing or requesting review on any personhog protocol changeset, when asked for an exhaustive or careful review of personhog code, and after any…