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 ReviewStage/stage-cli --skill stage-chaptersgit 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/stage-chapters)<a href="https://agentmods.dev/skills/reviewstage/stage-cli/stage-chapters"><img src="https://agentmods.dev/badge/skills/reviewstage/stage-cli/stage-chapters/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/stage-chapters"><img src="https://agentmods.dev/badge/skills/reviewstage/stage-cli/stage-chapters.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.00022 | $0.07539 |
| Opus 5.5 | $0.00009 | $0.03016 |
| Sonnet 5.5 | $0.00004 | $0.01508 |
| Haiku 4.5 | $0.00002 | $0.00754 |
Grade A, and why
stage-chapters 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 — 550 lines — stays where its author put it; the contents beside it link to each section on GitHub.
stage-chapters
Generates a Stage chapter run for the current local git branch and opens it in a browser. Uses stagereview prep to compute the diff, then generates chapters and a prologue, and hands the result to stagereview show to launch the SPA.
Prerequisites
Run these checks before any other work. If either fails, stop with the error message — do not continue.
-
stagereviewis installed. Runwhich stagereview. If it exits non-zero, instruct the user:stagereview is not installed. Run: npm install -g stagereview Then retry /stage-chapters.Stop.
-
The current directory is a git repo. Run
git rev-parse --is-inside-work-tree. If it does not printtrue, stop with:/stage-chapters must be run inside a git repository.
Step 1 — Run prep
PREP_FILE=$(stagereview prep)
stagereview prep auto-detects the base ref (main/master), computes the merge-base, generates the diff, filters out lockfiles/binaries, and formats hunks with line numbers for analysis. By default it auto-detects the diff scope: if uncommitted changes are present the diff includes staged, unstaged, and untracked files; otherwise it uses the committed branch diff. It writes a plain-text file and prints only the file path to stdout.
prep and show also accept positional git refs:
PREP_FILE=$(stagereview prep main)
PREP_FILE=$(stagereview prep main feature)
PREP_FILE=$(stagereview prep main..feature)
PREP_FILE=$(stagereview prep main...feature)
Use the same positional refs for show:
stagereview show "$AGENT_OUTPUT" main..feature
Both prep and show accept these optional flags:
--base <ref>— base ref to diff against (default: auto-detect main/master).--compare <ref>— compare ref to diff against--base.--ref <mode>— diff scope. One of:work— staged + unstaged + untracked changes (full working tree vs merge-base).staged— only staged changes (index vs HEAD).unstaged— only unstaged changes (working tree vs index).- Omitted — auto-detect (equivalent to
workwhen uncommitted changes exist, committed branch diff otherwise).
--pr <number-or-url>— review a GitHub pull request instead of the local branch. The base/head come from the PR itself, and its commits are fetched locally. Cannot be combined with positional refs,--base,--compare, or--ref. Requiresghto be installed and authenticated, and a github.comoriginremote. Useful for reviewing a teammate's PR you don't have checked out.
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 Changed · +10 lines 8995ac464b5b
- 1mo ago First seen · 540 lines · 22 tokens per session scan A 6bc1913a96c5
stage-chapters is a skill published in the GitHub repository ReviewStage/stage-cli (274 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 7,539 once invoked, about $0.0001 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
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.
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…