amend-plan

amend-plan is a command for Claude Code from closedloop-ai/claude-plugins. It costs 13 tokens per session (3,979 once invoked), scanned A, original, Apache-2.0.

A command for discussing and applying changes to an existing implementation plan. It keeps the amendment conversation in a state file so work can continue across runs.

In plain words
What is it for?
Use it to request changes to specific tasks, confirm amendments, and save those changes in the plan workflow.
Why use it?
It avoids editing plan tasks informally or losing the context of an unfinished plan change.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: reads .claude/ paths; names the TodoWrite tool.

Part of the code plugin — 15 skills, 7 commands, 23 agents, 7 hooks shipped together

Good fit Use it to request changes to specific tasks, confirm amendments, and save those changes in the plan workflow.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/closedloop-ai/claude-plugins/amend-plan
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.

Clone the repo
git clone --depth 1 https://github.com/closedloop-ai/claude-plugins

Made for: Claude Code.

Or install code, the plugin that ships this one along with the rest of its 15 skills, 7 commands, 23 agents, 7 hooks.

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 amend-plan

README.md
[![agentmods](https://agentmods.dev/badge/commands/closedloop-ai/claude-plugins/amend-plan.svg)](https://agentmods.dev/commands/closedloop-ai/claude-plugins/amend-plan)
Your own site
<a href="https://agentmods.dev/commands/closedloop-ai/claude-plugins/amend-plan"><img src="https://agentmods.dev/badge/commands/closedloop-ai/claude-plugins/amend-plan.svg" alt="Measured on agentmods" height="20"></a>
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,979 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.00013 $0.03979
Opus 5 $0.00006 $0.01989
Sonnet 5 $0.00003 $0.00796
Haiku 4.5 $0.00001 $0.00398

Measured yesterday against content hash 5b945614485c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

amend-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 yesterday.

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.

plugins/code/commands/amend-plan.md · 413 lines

How it starts

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

Experimental Plan Amend Command

Discuss and apply amendments to a plan.json implementation plan through natural conversation.

Role

When you invoke this command, you are the orchestrator. You handle the conversation directly, making edits when appropriate and using the state management script to persist conversation across workflow runs.

Usage

# With workdir (GitHub workflow passes this via $CLOSEDLOOP_WORKDIR)
/code:amend-plan --workdir .closedloop-ai/work --message "for task T-1.1, don't remove the SplashScreen.setLoadingInfo call"

# Auto-detect from $CLOSEDLOOP_WORKDIR or .closedloop-ai/work
/code:amend-plan --message "change the caching approach in T-2.1"

# With explicit state file
/code:amend-plan --workdir .closedloop-ai/work --state-file .closedloop-ai/work/amend-session.json --message "yes go ahead"

Options

  • --workdir <path> - Path to the work directory. If not provided, uses $CLOSEDLOOP_WORKDIR env var or defaults to .closedloop-ai/work
  • --message <text> - The user's message (required)
  • --state-file <path> - Path to amend session state file. Defaults to {workdir}/amend-session.json

Workflow

Use TodoWrite to track your progress through the amendment workflow:

TodoWrite([
  {"content": "Setup: Load state, read plan.json, add user message", "status": "pending", "activeForm": "Setting up amendment context"},
  {"content": "Analyze user intent (directive, question, or confirmation)", "status": "pending", "activeForm": "Analyzing user intent"},
  {"content": "Process request and determine response", "status": "pending", "activeForm": "Processing amendment request"},
  {"content": "Save response to state file", "status": "pending", "activeForm": "Saving response to state"},
  {"content": "Apply changes if confirmed (edit plan.json, regenerate plan.md, run apply)", "status": "pending", "activeForm": "Applying changes"}
])

Note: The last todo (Apply changes) only applies if the user gave a directive that was safe to apply, or confirmed a previously discussed change. Skip it if you're just answering a question or raising a concern.

Read the full file on GitHub · 413 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. yesterday First seen · 413 lines · 13 tokens per session scan A 5b945614485c

Subscribe to this mod's changes

amend-plan is a command published in the GitHub repository closedloop-ai/claude-plugins (103 stars, last pushed yesterday), licensed Apache-2.0. It adds 13 tokens to every session and 3,979 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-09-07.