A command that turns a feature request into an implementation plan with impact analysis, meaning a review of which parts of the codebase may be affected. It can accept input from a ticket or description and save the plan in the project.

Use it to explore a repository, identify affected areas, create a feature plan, and run the configured planning checks.

It helps reveal dependencies and the likely blast radius before coding begins. This gives the team a structured plan and review point for larger changes.

plan — Command for Claude Code by galando/temper

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code

/plugin marketplace add galando/temper

Claude Code

/plugin install temper

Made for: Claude Code.

Or install temper, the plugin that ships this one along with the rest of its 5 skills, 11 commands, 11 agents, 2 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/galando/temper/plan/github.svg)](https://agentmods.dev/commands/galando/temper/plan)

Your own site

<a href="https://agentmods.dev/commands/galando/temper/plan"><img src="https://agentmods.dev/badge/commands/galando/temper/plan/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/galando/temper/plan"><img src="https://agentmods.dev/badge/commands/galando/temper/plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 232 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.

Model	Per session	Once invoked
Fable 5.1	$0.00018	$0.00232
Opus 5.5	$0.00007	$0.00093
Sonnet 5.5	$0.00004	$0.00046
Haiku 4.5	$0.00002	$0.00023

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

Security

Grade A, and why

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 22d 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.

commands/plan.md · 18 lines

What it actually says

Plan

This command is a door into /temper: it starts a run (its Intent stage comes first, then Plan), or takes up the run that is active, and from there everything happens as /temper does it. There is one flow, and it is ${CLAUDE_PLUGIN_ROOT}/commands/temper.md.

Read ${CLAUDE_PLUGIN_ROOT}/commands/temper.md now and follow it exactly, entering at Plan as its section "Entering at a stage" says, with $ARGUMENTS as the feature to plan. That file was not filled in when you read it: wherever it writes the CLAUDE_PLUGIN_ROOT variable, use the folder that holds ${CLAUDE_PLUGIN_ROOT}/scripts/temper (that path with /scripts/temper taken off), and wherever it writes the ARGUMENTS variable, use $ARGUMENTS. Its first instruction (the enforcement line) applies here too.

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.

22d ago Changed · -68 lines · +10 tokens per session c840e8a755a8
1mo ago Changed · +20 lines c39168e61b23
1mo ago Changed · +1 lines 865a8f912bfc
2mo ago Changed 8450e674cf61
2mo ago First seen · 65 lines · 8 tokens per session scan A b77221ceba77

Subscribe to this mod's changes

plan is a command published in the GitHub repository galando/temper (18 stars, last pushed yesterday), licensed MIT. It adds 18 tokens to every session and 232 once invoked, about $0.0001 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.

Planning

plan next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
plangalando/temper	Command	18	yesterday	MIT	A	18	Claude Code
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	yesterday	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	yesterday	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	yesterday	MIT	A	14	Claude Code