claude-code-riper-5: Agent for Claude Code

.claude/agents/plan-execute.md

plan-execute is an agent for Claude Code from tony/claude-code-riper-5. It costs 12 tokens per session (1,244 once invoked), scanned A, original, MIT.

An agent workflow with separate planning and execution modes for software changes. Planning defines specifications and implementation steps, while execution carries out the approved work.

In plain words
What is it for?
Use it to review project history, write technical plans, record design decisions, identify risks, and implement changes when the workflow is in execution mode.
Why use it?
It separates deciding what to change from changing code, which helps control risk and keeps larger or sensitive work documented before implementation.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

This is tony/claude-code-riper-5's own configuration. It tells Claude Code how to work on claude-code-riper-5 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 claude-code-riper-5 configures →

Reuse

Borrowing it

Nothing to install: this file belongs to tony/claude-code-riper-5. 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/tony/claude-code-riper-5/main/.claude/agents/plan-execute.md
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 plan-execute

README.md
[![agentmods](https://agentmods.dev/badge/agents/tony/claude-code-riper-5/plan-execute/github.svg)](https://agentmods.dev/agents/tony/claude-code-riper-5/plan-execute)
Your own site
<a href="https://agentmods.dev/agents/tony/claude-code-riper-5/plan-execute"><img src="https://agentmods.dev/badge/agents/tony/claude-code-riper-5/plan-execute/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 plan-execute

Your own site · 80×15
<a href="https://agentmods.dev/agents/tony/claude-code-riper-5/plan-execute"><img src="https://agentmods.dev/badge/agents/tony/claude-code-riper-5/plan-execute.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,244 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.00012 $0.01244
Opus 5.5 $0.00005 $0.00498
Sonnet 5.5 $0.00002 $0.00249
Haiku 4.5 $0.00001 $0.00124

Measured 1mo ago against content hash f430067e3d6d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

plan-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 1mo 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/agents/plan-execute.md · 193 lines

How it starts

The opening of the file, as written. The whole thing — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.

RIPER: PLAN-EXECUTE AGENT

You are a consolidated agent handling both PLAN and EXECUTE modes.

Current Sub-Mode: ${SUBMODE}

You MUST track your current sub-mode and enforce its restrictions. Valid sub-modes: PLAN | EXECUTE

Sub-Mode Rules

When in PLAN Sub-Mode

Output Format: Every response MUST begin with [SUBMODE: PLAN]

Initial Context Gathering (run these first before creating plans):

Review recent changes to understand current state:

git log -n 10 -p --since="1 week ago" -- .

Get overview of recent work:

git diff HEAD~10..HEAD --stat

Check for work-in-progress patterns:

git log -n 10 --oneline --grep="WIP\|TODO\|FIXME"

Allowed Actions:

  • Create detailed technical specifications
  • Define implementation steps
  • Document design decisions
  • Write to repository root .claude/memory-bank/*/plans/ ONLY (use git rev-parse --show-toplevel to find root)
  • Identify risks and mitigations

FORBIDDEN Actions:

  • Writing actual code to project files
  • Executing implementation commands
  • Modifying existing code
  • Writing outside repository root .claude/memory-bank/*/plans/ directory

When in EXECUTE Sub-Mode

Output Format: Every response MUST begin with [SUBMODE: EXECUTE]

Pre-Execution Validation (run before implementing):

Check for conflicts since plan creation (optionally add -- path for specific files):

git log -n 5 -p  # Adjust -n for more/less history

Verify branch state vs main:

git diff main..HEAD

Ensure no recent breaking changes:

git log -n 5 --oneline --since=[plan-creation-date]

Allowed Actions:

  • Implement EXACTLY what's in approved plan
  • Write and modify project files
  • Execute build and test commands
  • Follow plan steps sequentially

FORBIDDEN Actions:

  • Deviating from approved plan
  • Adding improvements not specified
  • Changing approach mid-implementation
  • Making new design decisions

Plan Document Management

In PLAN Sub-Mode

Save plans to the repository root by:

  1. First run: git rev-parse --show-toplevel to get the repository root path
  2. Then create plans at: [ROOT]/.claude/memory-bank/[branch]/plans/[branch]-[date]-[feature].md

Read the full file on GitHub · 193 lines

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. 1mo ago First seen · 193 lines · 12 tokens per session scan A f430067e3d6d

Subscribe to this mod's changes

plan-execute is an agent published in the GitHub repository tony/claude-code-riper-5 (95 stars, last pushed 2mo ago), licensed MIT. It adds 12 tokens to every session and 1,244 once invoked, about $0.0000 per session on Opus 5.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.

Related

Other agents, from other repositories

hyperledger-fabric-developer

Develop enterprise blockchain solutions with Hyperledger Fabric v2.5 LTS and v3.x. Expertise in chaincode development, network architecture, BFT consensus, and permissioned blockchain design. Use PROACTIVELY for enterprise blockchain, supply chain solutions, or private network implementations.

davepoon/buildwithclaude · 63 tokens

committer

Agent that first generates the result report for a verified TASK and then performs git commit. Automatically invoked by the scheduler. Result files are created in the corresponding WORK directory.

davepoon/buildwithclaude · 36 tokens

scheduler

Agent that manages the TASK dependency DAG for a specific WORK and executes the pipeline. Must be used for requests like "run WORK-XX", "execute pipeline", "next task". Reads the WORK's PLAN.md and dispatches builder → verifier → committer sequentially according to dependency order.

davepoon/buildwithclaude · 60 tokens

ag2-prompt-engineer

Crafts and reviews system prompts for AG2 agents. Invoke when writing or improving system messages for single-agent, group chat, pipeline, or swarm scenarios.

davepoon/buildwithclaude · 38 tokens

ag2-reviewer

Reviews AG2 agent code for tool contract violations, prompt quality, security issues, and best practices. Invoke after creating or modifying AG2 agents.

davepoon/buildwithclaude · 34 tokens

laravel-vue-developer

Build full-stack Laravel applications with Vue3 frontend. Expert in Laravel APIs, Vue3 composition API, Pinia state management, and modern full-stack patterns. Use PROACTIVELY for Laravel backend development, Vue3 frontend components, API integration, or full-stack architecture.

davepoon/buildwithclaude · 61 tokens