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-interview/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-interview)<a href="https://agentmods.dev/skills/jstxn/rein/rein-interview"><img src="https://agentmods.dev/badge/skills/jstxn/rein/rein-interview/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-interview"><img src="https://agentmods.dev/badge/skills/jstxn/rein/rein-interview.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.00021 | $0.02248 |
| Opus 5 | $0.00010 | $0.01124 |
| Sonnet 5 | $0.00004 | $0.00450 |
| Haiku 4.5 | $0.00002 | $0.00225 |
Grade A, and why
rein-interview 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.
How it starts
The opening of the file, as written. The whole thing — 333 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<Use_When>
- The request is underspecified, risky, or likely to cause misaligned implementation
- The user wants clarification before planning or coding
- You need durable interview state, resumability, or machine-readable handoff artifacts
- You need a spec bundle that can feed
rein-plan, direct implementation, or further refinement </Use_When>
<Do_Not_Use_When>
- The request already has concrete file targets and stable acceptance criteria
- The user explicitly asks to skip clarification and execute immediately
- A complete rein-interview spec already exists and the next step should begin </Do_Not_Use_When>
<Runtime_Contract> The runtime owns:
- durable state under
.rein/state/ - context snapshots under
.rein/context/ - clarity score computation
- readiness gates
- round ordering
- status display
- transcript/spec/result bundle output
You own:
- asking the next question
- interpreting the user's answer
- deciding the next target dimension
- framing the next question in your own judgment and voice
- producing the final structured summary payload for crystallization </Runtime_Contract>
<Execution_Policy>
- Ask one question per round, never batch
- Stay intent-first until scope, non-goals, and decision boundaries are explicit
- Use runtime state at every transition point; do not keep the authoritative interview state only in prose
- Show the user current clarity progress after each runtime update
- Do not crystallize until threshold and readiness gates are satisfied, unless the user explicitly accepts the risk
- Do not implement directly inside rein-interview
- Use runtime suggestions for structure, but choose the actual next question yourself </Execution_Policy>
<Interview_Presentation_Contract> Use a consistent chat-safe presentation frame for every visible interview turn.
Layout
Normal round:
[ Interview ]
| Phase: clarifying structure
| Current clarity: N%
| Question
| [one to two short lines]
|
| A. ...
| B. ...
| C. ...
Open-question variant:
[ Interview ]
| Phase: clarifying structure
| Current clarity: N%
| Question
| [one to two short lines]
Review:
[ Review ]
| Phase: confirming summary
| Current clarity: N%
| Question
| [one to two short lines]
Handoff:
[ Handoff ]
| Phase: preparing handoff
| Status: ready for handoff
| Question
| [one to two short lines]
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 · 333 lines · 21 tokens per session scan A a5761ba2b488
rein-interview is a skill published in the GitHub repository jstxn/rein (12 stars, last pushed 4mo ago), licensed MIT. It adds 21 tokens to every session and 2,248 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.
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…