Borrowing it
Nothing to install: this file belongs to ReviewStage/stage-cli. 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/ReviewStage/stage-cli/main/.agents/skills/iterate-pr/SKILL.mdgit clone --depth 1 https://github.com/ReviewStage/stage-cliWrote 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/reviewstage/stage-cli/iterate-pr)<a href="https://agentmods.dev/skills/reviewstage/stage-cli/iterate-pr"><img src="https://agentmods.dev/badge/skills/reviewstage/stage-cli/iterate-pr/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/reviewstage/stage-cli/iterate-pr"><img src="https://agentmods.dev/badge/skills/reviewstage/stage-cli/iterate-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 26 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 56 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00046 | $0.01043 |
| Opus 5.5 | $0.00018 | $0.00417 |
| Sonnet 5.5 | $0.00009 | $0.00209 |
| Haiku 4.5 | $0.00005 | $0.00104 |
Grade A, and why
iterate-pr 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 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.
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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Iterate PR
Recurring loop that checks a PR each iteration and fixes what's broken. Combines /fixing-pr-comments, /fixing-ci, and /rebase-origin-main.
WHEN INVOKED — Do These Two Steps Immediately
STEP 1: Run the iteration checklist once right now (before setting up the loop).
Execute all condition checks, run the appropriate sub-skills, and report results. Do not skip this — the first pass must happen immediately in the current session.
STEP 2: After reporting results, always kick off the loop using /loop at the requested interval (default 10m):
/loop <INTERVAL> For PR #<NUM> (<OWNER>/<REPO>): run the iterate-pr iteration sequence — check PR state, check for merge conflicts, check for unresolved comments, check for failing CI. Fix what's broken. Cancel the loop when the PR is closed or merged, OR when ALL of the following are simultaneously true: no merge conflicts with origin/main, zero unresolved review threads, no failing CI checks, no pending CI checks, and no commit was pushed this iteration.
Replace <INTERVAL> with the interval passed to /iterate-pr (default 10m), and <NUM>, <OWNER>, <REPO> with the actual values resolved in Step 1. Do not leave placeholders.
The loop is mandatory. Never ask the user whether to set it up — always set it up.
Both steps are mandatory. The loop is not a substitute for Step 1 — it is in addition to it.
Iteration Sequence
Each iteration (including the first one in Step 1 above) follows this sequence:
1. VERIFY → gh pr view; stop loop if closed/merged
2. REBASE → If merge conflicts with origin/main → /rebase-origin-main
3. COMMENTS → If unresolved threads → /fixing-pr-comments
4. CI → If CI failing → /fixing-ci
5. REPORT → Summarize what was checked and what was done (or skipped).
Cancel the loop when ANY of the following is true:
- PR is closed or merged
- ALL of the following are simultaneously true:
- No merge conflicts with origin/main
- Zero unresolved review threads
- No failing CI checks
- No pending CI checks
- No commit was pushed this iteration
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 · 97 lines · 46 tokens per session scan A c5083e0cb917
iterate-pr is a skill published in the GitHub repository ReviewStage/stage-cli (274 stars, last pushed 1mo ago), licensed MIT. It adds 46 tokens to every session and 1,043 once invoked, about $0.0002 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
pr
Draft a PR body from OMC's paper trail — the smallest visual that proves the change, evidence consumed from the verify protocol (never re-collected), reversibility from the ADR test on the diff, glossary language throughout.
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
otto-pr-review-loop
Run Polly and OCR on a PR until all findings settle.
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
A step-by-step guide for contributing code, tests, documentation, or build changes to open-source projects you do not maintain. It explains how to prepare a pull request that follows the project’s rules and is easier for maintainers to review.