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/.claude/commands/rein-scope.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/commands/jstxn/rein/rein-scope)<a href="https://agentmods.dev/commands/jstxn/rein/rein-scope"><img src="https://agentmods.dev/badge/commands/jstxn/rein/rein-scope.svg" alt="Measured on agentmods" 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 8d 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.
- 8d ago First seen · 46 lines · 31 tokens per session scan A 6544b5bf0814
rein-scope is a command 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.