A command that creates a detailed plan for a software change before any code is written.

It plans frontend and backend changes, including possible effects on communication, state, terminals, databases, and Windows support.

It clarifies requirements, affected files, risks, dependencies, and checks before implementation begins.

How talayash/agentrium configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to talayash/agentrium. 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/talayash/agentrium/master/.claude/commands/plan.md

Clone the repo

git clone --depth 1 https://github.com/talayash/agentrium

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.

README.md

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

Your own site

<a href="https://agentmods.dev/commands/talayash/agentrium/plan"><img src="https://agentmods.dev/badge/commands/talayash/agentrium/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/talayash/agentrium/plan"><img src="https://agentmods.dev/badge/commands/talayash/agentrium/plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 293 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.00000	$0.00293
Opus 5.5	$0.00000	$0.00117
Sonnet 5.5	$0.00000	$0.00059
Haiku 4.5	$0.00000	$0.00029

Measured 1mo ago against content hash 38f354cf2be8, 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 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/commands/plan.md · 48 lines

What it actually says

Plan

Create a detailed implementation plan before writing any code.

Instructions

You are about to plan the implementation of: $ARGUMENTS

Follow this process strictly:

Step 1: Restate Requirements

Restate what the user wants in your own words
List specific acceptance criteria
Identify any ambiguities - ask if unclear

Step 2: Assess Current State

Read relevant files in src/ (frontend) and src-tauri/src/ (backend)
Identify ALL files that will need changes
Note existing patterns to follow

Step 3: Risk Assessment

Evaluate:

Breaking changes to IPC contracts?
New Zustand store fields needed?
PTY/terminal lifecycle impact?
Database schema changes?
Windows-specific concerns?

Step 4: Create Phased Plan

For each phase:

Files to modify/create (exact paths)
What changes in each file
Dependencies between phases
How to verify the phase works

Step 5: Present Plan

Format as:

# Plan: [Feature Name]
## Requirements: ...
## Risk Assessment: ...
## Phase 1: [Name] - Files, Changes, Test
## Phase 2: [Name] - Files, Changes, Test
## Complexity: S/M/L/XL

WAIT for user confirmation before implementing. Ask: "Does this plan look good?"

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.

1mo ago First seen · 48 lines · 0 tokens per session scan A 38f354cf2be8

Subscribe to this mod's changes

plan is a command published in the GitHub repository talayash/agentrium (46 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 293 tokens. 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.

Claude Code Planning Productivity Writing and docs builders grid-view profiles vibe-coding

agentrium: Command for Claude Code