plan

plan is a command for Claude Code from d-kimuson/claude-code-viewer. It costs 9 tokens per session (349 once invoked), scanned A, original, MIT.

A task-planning command for breaking complex software work into ordered steps, including implementation and checks.

In plain words
What is it for?
Use it to inspect a codebase, plan a feature or bug fix, and organize testing, documentation, build, and deployment tasks.
Why use it?
It turns a broad development request into a clear checklist with dependencies and verification work, so important steps are less likely to be missed.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the TodoWrite tool.

Good fit Use it to inspect a codebase, plan a feature or bug fix, and organize testing, documentation, build, and deployment tasks.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/d-kimuson/claude-code-viewer/plan
About the project

Claude Code Viewer is a web client for managing Claude Code projects, including starting or resuming conversations, monitoring tasks, and browsing session history. Its catalogue entries provide skills, commands, hooks, instructions, and settings that extend the client’s workflow.

d-kimuson/claude-code-viewer · 1,300 stars · on GitHub · npmjs.com

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/d-kimuson/claude-code-viewer

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

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

agentmods 80×15 button for plan

Your own site · 80×15
<a href="https://agentmods.dev/commands/d-kimuson/claude-code-viewer/plan"><img src="https://agentmods.dev/badge/commands/d-kimuson/claude-code-viewer/plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 349 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.00009 $0.00349
Opus 5.5 $0.00004 $0.00140
Sonnet 5.5 $0.00002 $0.00070
Haiku 4.5 $0.00001 $0.00035

Measured 1mo ago against content hash 3bc93c4b5053, 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.

mock-global-claude-dir/commands/plan.md · 49 lines

What it actually says

Create a comprehensive task plan for the given development work. Break down complex tasks into manageable, actionable steps.

Planning Process

  1. Analysis Phase

    • Use Read, Grep, and Glob tools to understand the current codebase
    • Identify existing patterns, conventions, and dependencies
    • Check git status to understand current state
  2. Task Breakdown

    • Decompose the main objective into specific, actionable tasks
    • Each task should be completable within a reasonable timeframe
    • Include both implementation and verification steps
  3. Create Todo List

    • Use TodoWrite tool to create a structured task list
    • Set all tasks to "pending" status initially
    • Include both content (imperative form) and activeForm (present continuous)
    • Order tasks by logical dependency and priority
  4. Task Categorization

    • Implementation tasks (new features, bug fixes)
    • Testing and verification tasks
    • Documentation updates (if required)
    • Build and deployment tasks

Task Planning Guidelines

  • Make tasks specific and measurable
  • Include prerequisite checks where needed
  • Add validation steps after implementation
  • Consider potential blockers and alternatives
  • Ensure each task has clear completion criteria

Example Task Structure

For each task in the todo list:

  • content: "Implement user authentication middleware"
  • activeForm: "Implementing user authentication middleware"
  • status: "pending"

Always start with research and analysis tasks before moving to implementation.

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 · 49 lines · 9 tokens per session scan A 3bc93c4b5053

Subscribe to this mod's changes

plan is a command published in the GitHub repository d-kimuson/claude-code-viewer (1,300 stars, last pushed 2mo ago), licensed MIT. It adds 9 tokens to every session and 349 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.