implement_plan

implement_plan is a command for coding agents from hoblin/claude-ruby-marketplace. It costs 12 tokens per session (680 once invoked), scanned A, original, MIT.

A command for carrying out an approved technical plan stored in the repository. It reads the plan and related files, tracks phases, implements the work, and verifies each result.

In plain words
What is it for?
Use it to execute a plan, update its progress markers, make the specified changes, and check the finished work.
Why use it?
It keeps implementation aligned with an agreed plan while handling differences found in the codebase.

Command

Part of the rpi plugin — 12 commands, 12 agents shipped together

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/hoblin/claude-ruby-marketplace/implement_plan
Clone the repo
git clone --depth 1 https://github.com/hoblin/claude-ruby-marketplace

Or install rpi, the plugin that ships this one along with the rest of its 12 commands, 12 agents.

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 implement_plan

README.md
[![agentmods](https://agentmods.dev/badge/commands/hoblin/claude-ruby-marketplace/implement_plan.svg)](https://agentmods.dev/commands/hoblin/claude-ruby-marketplace/implement_plan)
Your own site
<a href="https://agentmods.dev/commands/hoblin/claude-ruby-marketplace/implement_plan"><img src="https://agentmods.dev/badge/commands/hoblin/claude-ruby-marketplace/implement_plan.svg" alt="Measured on agentmods" 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 680 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.00012 $0.00680
Opus 5 $0.00006 $0.00340
Sonnet 5 $0.00002 $0.00136
Haiku 4.5 $0.00001 $0.00068

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

Security

Grade A, and why

implement_plan 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 3d 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.

Origin

Copies of this mod

2 near-identical copies found in the catalogue:

plugins/rpi/commands/implement_plan.md · 87 lines

How it starts

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

Implement Plan

You are tasked with implementing an approved technical plan from ./thoughts/shared/plans/. These plans contain phases with specific changes and success criteria.

Getting Started

When given a plan path:

  • Read the plan completely and check for any existing checkmarks (- [x])
  • Read the original ticket and all files mentioned in the plan
  • Read files fully - never use limit/offset parameters, you need complete context
  • Think deeply about how the pieces fit together
  • Create a todo list to track your progress
  • Start implementing if you understand what needs to be done

If no plan path provided, ask for one.

Implementation Philosophy

Plans are carefully designed, but reality can be messy. Your job is to:

  • Follow the plan's intent while adapting to what you find
  • Implement each phase fully before moving to the next
  • Verify your work makes sense in the broader codebase context
  • Update checkboxes in the plan as you complete sections

When things don't match the plan exactly, think about why and communicate clearly. The plan is your guide, but your judgment matters too.

If you encounter a mismatch:

  • STOP and think deeply about why the plan can't be followed
  • Present the issue clearly:
    Issue in Phase [N]:
    Expected: [what the plan says]
    Found: [actual situation]
    Why this matters: [explanation]
    
    How should I proceed?
    

Verification Approach

After implementing a phase:

  • Run the success criteria checks (usually make check test covers everything)
  • Fix any issues before proceeding
  • Update your progress in both the plan and your todos
  • Check off completed items in the plan file itself using Edit
  • Pause for human verification: After completing all automated verification for a phase, pause and inform the human that the phase is ready for manual testing. Use this format:
    Phase [N] Complete - Ready for Manual Verification
    
    Automated verification passed:
    - [List automated checks that passed]
    
    Please perform the manual verification steps listed in the plan:
    - [List manual verification items from the plan]
    
    Let me know when manual testing is complete so I can proceed to Phase [N+1].
    

Read the full file on GitHub · 87 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. 3d ago First seen · 87 lines · 12 tokens per session scan A 082b4513752f

Subscribe to this mod's changes

implement_plan is a command published in the GitHub repository hoblin/claude-ruby-marketplace (36 stars, last pushed 24d ago), licensed MIT. It adds 12 tokens to every session and 680 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.