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 eric-tramel/moraine --skill code-review-scopegit clone --depth 1 https://github.com/eric-tramel/moraineWrote 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/eric-tramel/moraine/code-review-scope)<a href="https://agentmods.dev/skills/eric-tramel/moraine/code-review-scope"><img src="https://agentmods.dev/badge/skills/eric-tramel/moraine/code-review-scope/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/eric-tramel/moraine/code-review-scope"><img src="https://agentmods.dev/badge/skills/eric-tramel/moraine/code-review-scope.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.00321 |
| Opus 5.5 | $0.00019 | $0.00128 |
| Sonnet 5.5 | $0.00010 | $0.00064 |
| Haiku 4.5 | $0.00005 | $0.00032 |
Grade A, and why
code-review-scope 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.
What it actually says
CodeReviewScope
Persona
Review for scope control. Compare the stated purpose with the actual diff and call out unrelated changes that make the PR harder to review, test, or revert.
Focus
- Identify files, modules, migrations, config, docs, or UI changes that do not support the stated goal.
- Separate required enabling changes from opportunistic cleanup.
- Flag mixed concerns such as feature work plus broad refactors, formatting churn, dependency changes, or unrelated docs updates.
- Check whether operational impact, migrations, and behavior changes are disclosed in the PR body.
- Recommend splitting only when it reduces review risk or deployment risk.
Non-Goals
Do not block small local cleanup that directly clarifies the changed code. Do not require splitting changes that are tightly coupled and safer to land together.
Output
Lead with scope crossings and the split or narrowing recommendation:
- [P2] Split the monitor restyle from the MCP filtering fix
`web/monitor/styles.css:1`
The PR is scoped to MCP project filtering, but half the diff changes monitor
colors and spacing. Moving the restyle to a separate PR keeps the filtering
fix easier to review and revert.
If there are no scope findings, say the PR stays within its stated scope.
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.
- 1mo ago First seen · 37 lines · 48 tokens per session scan A 40ac4a20588a
code-review-scope is a skill published in the GitHub repository eric-tramel/moraine (116 stars, last pushed 12d ago), licensed Apache-2.0. It adds 48 tokens to every session and 321 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
sage-review
Deep, platform-neutral code review for PRs and CRs in ONE thorough single pass — design reasoning (Problem Worth Solving & Solution Fit) as one dimension alongside the 9 code-level dimensions, with chain-of-consequences, self-critique, and draft-only comments. The single app-owned source of truth.
learn-from-sage
Detection-gap (miss) analysis for Code Review Sage. Learn from shipped fixes, acted-on human comments, and design outcomes to close reviewer blind spots. Inline during review stages a candidate; a human triggers a one-shot AI consolidation into the live ruleset.
pr-review
Review a GitHub pull request using multiple expert personas. Takes a PR URL as input, analyzes the changes, and generates comprehensive review feedback from different perspectives (Merge Specialist, Frontend, Backend, Security, DevOps, AI/Agent, SRE, Chief Architect).
review-fix-signoff-loop
Use when writing Agent Relay or Ricky workflows that must loop review, fix, and validation with fresh agent context until independent signoff agents, typically Claude and Codex, both agree the work is comprehensively complete. Covers fresh-context iterations, repairable gates, dual reviewer verdict contracts…
github-review-pr
Review GitHub pull requests with detailed, multi-perspective code analysis using parallel subagents. Use this skill whenever the user wants to review a PR, asks for code review on a pull request, mentions "review PR", "check this PR", "look at pull request", or references a PR number or GitHub PR URL. Do NOT use for…
code-review
Reviewing code for defects: diff-first reading, severity classification, evidence over inference, finding caps, and terminal verdicts. Use when reviewing a diff, PR, or patch, or auditing someone else's work.