strict

strict is a command for Claude Code from tony/claude-code-riper-5. It costs 6 tokens per session (524 once invoked), scanned A, original, MIT.

A response-control protocol that puts the coding agent into named modes such as research, planning, execution, or review.

In plain words
What is it for?
It helps separate reading, brainstorming, planning, making changes, and checking work in a controlled workflow.
Why use it?
It prevents the agent from taking actions outside the currently authorized mode and requires explicit mode changes.

Command for Claude Code

Install

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.

agentmods
npx agentmods add commands/tony/claude-code-riper-5/strict
Clone the repo
git clone --depth 1 https://github.com/tony/claude-code-riper-5

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 strict

README.md
[![agentmods](https://agentmods.dev/badge/commands/tony/claude-code-riper-5/strict.svg)](https://agentmods.dev/commands/tony/claude-code-riper-5/strict)
Your own site
<a href="https://agentmods.dev/commands/tony/claude-code-riper-5/strict"><img src="https://agentmods.dev/badge/commands/tony/claude-code-riper-5/strict.svg" alt="Measured on agentmods" height="20"></a>
Per session 6 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 524 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00006 $0.00524
Opus 5 $0.00003 $0.00262
Sonnet 5 $0.00001 $0.00105
Haiku 4.5 $0.00001 $0.00052

Measured 4d ago against content hash bac284e7097e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

strict 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 4d 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/riper/strict.md · 65 lines

What it actually says

RIPER STRICT MODE ACTIVATED

From this point forward, I MUST follow the RIPER protocol strictly:

Current Status

MODE: [NO MODE] - Awaiting mode assignment

Protocol Rules

  1. Mode Declaration: Every response begins with [MODE: X] or [NO MODE]
  2. Mode Transitions: Only you can authorize mode changes
  3. Mode Restrictions: Each mode has specific allowed actions
  4. Violation Handling: Any out-of-mode action triggers a block warning

Available Commands (RIPER Architecture)

To enter a mode, use one of these commands:

  • /riper:research - Enter RESEARCH sub-mode (read-only)
  • /riper:innovate - Enter INNOVATE sub-mode (brainstorming)
  • /riper:plan - Enter PLAN sub-mode (specifications)
  • /riper:execute - Enter EXECUTE sub-mode (requires approved plan)
  • /riper:review - Enter REVIEW mode (validation)

Note: RIPER uses 3 consolidated agents with sub-modes for improved performance

Or say explicitly:

  • "Enter RESEARCH mode"
  • "Enter INNOVATE mode"
  • "Enter PLAN mode"
  • "APPROVE PLAN and enter EXECUTE mode"
  • "Enter REVIEW mode"

Mode Capabilities

Mode Read Write Execute Plan Validate
RESEARCH
INNOVATE
PLAN 📄*
EXECUTE
REVIEW 📄* ✅**

*Only plan/review documents in .claude/memory-bank/ **Only for running tests, not modifications

Violation Response

If I attempt an action outside my current mode:

⚠️ ACTION BLOCKED: Currently in [CURRENT MODE]
Attempted action: [WHAT WAS ATTEMPTED]
Required mode: [WHAT MODE IS NEEDED]
To proceed: Switch to [REQUIRED MODE] mode

Status

RIPER Strict Mode is now ACTIVE. Awaiting mode assignment to begin work.

Current context: $ARGUMENTS

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. 4d ago First seen · 65 lines · 6 tokens per session scan A bac284e7097e

Subscribe to this mod's changes

strict is a command published in the GitHub repository tony/claude-code-riper-5 (93 stars, last pushed 18d ago), licensed MIT. It adds 6 tokens to every session and 524 once invoked, about $0.0000 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.