rein: Command for Claude Code

.claude/commands/rein-triage.md

rein-triage is a command for Claude Code from jstxn/rein. It costs 27 tokens per session (178 once invoked), scanned A, original, MIT.

A preparation checklist for ambiguous, broad, or risky coding tasks that may affect several files. It identifies relevant files, assumptions, success criteria, and limits on acceptable shortcuts.

In plain words
What is it for?
Use it before editing a codebase to outline what to inspect, what must be true when finished, and what would count as cheating or unsupported claims.
Why use it?
It prevents coding from starting with hidden assumptions or an unclear definition of success. It also makes it easier to stop when the task is impossible or contradictory.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is jstxn/rein's own configuration. It tells Claude Code how to work on rein itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything rein configures →

View source ↗ jstxn/rein
Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/jstxn/rein/main/.claude/commands/rein-triage.md
Clone the repo
git clone --depth 1 https://github.com/jstxn/rein

Made for: Claude Code.

Wrote 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.

agentmods badge for rein-triage

README.md
[![agentmods](https://agentmods.dev/badge/commands/jstxn/rein/rein-triage/github.svg)](https://agentmods.dev/commands/jstxn/rein/rein-triage)
Your own site
<a href="https://agentmods.dev/commands/jstxn/rein/rein-triage"><img src="https://agentmods.dev/badge/commands/jstxn/rein/rein-triage/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.

agentmods 80×15 button for rein-triage

Your own site · 80×15
<a href="https://agentmods.dev/commands/jstxn/rein/rein-triage"><img src="https://agentmods.dev/badge/commands/jstxn/rein/rein-triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 27 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 178 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00027 $0.00178
Opus 5 $0.00014 $0.00089
Sonnet 5 $0.00005 $0.00036
Haiku 4.5 $0.00003 $0.00018

Measured 12d ago against content hash 50d35d1e093e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

rein-triage 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 12d 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.

.claude/commands/rein-triage.md · 29 lines

What it actually says

rein-triage

Use this before editing when the task is ambiguous, broad, risky, or likely to touch multiple files.

Steps

  1. Read the task and identify the most likely relevant files.
  2. State the top assumptions.
  3. Separate verified facts from unverified assumptions.
  4. Define what success looks like.
  5. Define what would count as cheating, bluffing, or reward hacking.
  6. If the task is impossible or conflicting, stop and report the conflict instead of forcing a pass.

Output

Emit a short triage note with:

  • relevant files
  • verified assumptions
  • open assumptions
  • success definition
  • cheating boundary
  • stop-and-report trigger, if any
Changes

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.

  1. 12d ago First seen · 29 lines · 27 tokens per session scan A 50d35d1e093e

Subscribe to this mod's changes

rein-triage is a command published in the GitHub repository jstxn/rein (12 stars, last pushed 4mo ago), licensed MIT. It adds 27 tokens to every session and 178 once invoked, about $0.0001 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.