execute

A command for entering execute mode to carry out an approved implementation plan. It tells the agent to find the latest plan for the current branch and follow its steps exactly.

In plain words
What is it for?
Use it when a plan has already been approved and you want the agent to implement that plan in order.
Why use it?
It prevents implementation work from drifting away from the agreed scope or adding unapproved changes. Problems that block a step are reported instead of being silently bypassed.

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/execute
Clone the repo
git clone --depth 1 https://github.com/tony/claude-code-riper-5

Made for: Claude Code.

Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 102 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.00008 $0.00102
Opus 5 $0.00004 $0.00051
Sonnet 5 $0.00002 $0.00020
Haiku 4.5 $0.00001 $0.00010

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

Security

Grade A, and why

execute 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 2d 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/execute.md · 16 lines

What it actually says

⚠️ EXECUTE MODE REQUIRES APPROVED PLAN

Activate the plan-execute agent in EXECUTE sub-mode to implement the approved plan.

Task context: $ARGUMENTS

The agent will operate in EXECUTE sub-mode:

  1. Locate the most recent approved plan for the current branch
  2. Execute each step exactly as specified
  3. Report any blocks or issues

Remember: NO deviations from the approved plan are allowed.

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. 2d ago First seen · 16 lines · 8 tokens per session scan A b51e9e9e2a30

Subscribe to this mod's changes

execute is a command published in the GitHub repository tony/claude-code-riper-5 (93 stars, last pushed 17d ago), licensed MIT. It adds 8 tokens to every session and 102 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.