Borrowing it
Nothing to install: this file belongs to jstxn/rein. 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/jstxn/rein/main/.codex/skills/rein-scope/SKILL.mdgit clone --depth 1 https://github.com/jstxn/reinWrote 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/jstxn/rein/rein-scope)<a href="https://agentmods.dev/skills/jstxn/rein/rein-scope"><img src="https://agentmods.dev/badge/skills/jstxn/rein/rein-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/jstxn/rein/rein-scope"><img src="https://agentmods.dev/badge/skills/jstxn/rein/rein-scope.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00031 | $0.00339 |
| Opus 5 | $0.00015 | $0.00169 |
| Sonnet 5 | $0.00006 | $0.00068 |
| Haiku 4.5 | $0.00003 | $0.00034 |
Grade A, and why
rein-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 10d 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
rein-scope
Use this when the work as stated is too large for a single pass, contains contradictions, or needs explicit boundaries before implementation begins.
When To Use
- The request implies more work than can be safely completed in one session
- Requirements contradict each other or contradict existing behavior
- The user asks for everything but constraints demand tradeoffs
- Scope creep is likely without an explicit boundary
When Not To Use
- The task is already well-scoped with clear acceptance criteria
- Deep-interview has already produced a spec with explicit non-goals
- The user explicitly asks to skip scoping
Steps
- Restate the full request as understood.
- Identify every distinct deliverable implied by the request.
- Classify each deliverable:
- must: required for the work to be considered complete
- should: valuable but deferrable without breaking the core intent
- will not: explicitly out of scope for this pass
- For each contradiction or tension, state the conflict and propose a resolution with tradeoffs.
- Identify what information is missing to commit to the scope.
- Present the scope contract for user confirmation before proceeding.
Output
Emit a scope contract with:
- restated request
- must / should / will-not classification
- conflicts identified and proposed resolutions
- missing information
- explicit confirmation request
Do not begin implementation until the user confirms the scope 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.
- 10d ago First seen · 46 lines · 31 tokens per session scan A 6544b5bf0814
rein-scope is a skill published in the GitHub repository jstxn/rein (12 stars, last pushed 4mo ago), licensed MIT. It adds 31 tokens to every session and 339 once invoked, about $0.0002 per session on Opus 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…