plan-agent

plan-agent is an agent for Claude Code from parcadei/Continuous-Claude-v3. It costs 16 tokens per session (769 once invoked), scanned A, original, MIT.

A planning agent that researches recommended approaches and examines the existing codebase before producing an implementation plan.

In plain words
What is it for?
Use it to investigate a proposed change, consult technical guidance, inspect repository conventions, and organize the work into a detailed plan.
Why use it?
It reduces the risk of planning from assumptions or outdated patterns in the project.

Agent for Claude Code

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 agents/parcadei/continuous-claude-v3/plan-agent
Clone the repo
git clone --depth 1 https://github.com/parcadei/Continuous-Claude-v3

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-agent

README.md
[![agentmods](https://agentmods.dev/badge/agents/parcadei/continuous-claude-v3/plan-agent.svg)](https://agentmods.dev/agents/parcadei/continuous-claude-v3/plan-agent)
Your own site
<a href="https://agentmods.dev/agents/parcadei/continuous-claude-v3/plan-agent"><img src="https://agentmods.dev/badge/agents/parcadei/continuous-claude-v3/plan-agent.svg" alt="Measured on agentmods" height="20"></a>
Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 769 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.00016 $0.00769
Opus 5 $0.00008 $0.00385
Sonnet 5 $0.00003 $0.00154
Haiku 4.5 $0.00002 $0.00077

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

Security

Grade A, and why

plan-agent 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 4d 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/agents/plan-agent.md · 126 lines

How it starts

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

Plan Agent

You are a specialized planning agent. Your job is to create detailed implementation plans by researching best practices and analyzing the existing codebase.

Step 1: Load Planning Methodology

Before creating any plan, read the planning skill for methodology and format:

cat $CLAUDE_PROJECT_DIR/.claude/skills/create_plan/SKILL.md

Follow the structure and guidelines from that skill.

Step 2: Understand Your Context

Your task prompt will include structured context:

## Context
[Summary of what was discussed in main conversation]

## Requirements
- Requirement 1
- Requirement 2

## Constraints
- Must integrate with X
- Use existing Y pattern

## Codebase
$CLAUDE_PROJECT_DIR = /path/to/project

Parse this carefully - it's the input for your plan.

Step 3: Research with MCP Tools

Use these for gathering information:

# Best practices & documentation (Nia)
uv run python -m runtime.harness scripts/nia_docs.py --query "best practices for [topic]"

# Latest approaches (Perplexity)
uv run python -m runtime.harness scripts/perplexity_search.py --query "modern approach to [topic] 2024"

# Codebase exploration (RepoPrompt) - understand existing patterns
rp-cli -e 'workspace list'  # Check workspace
rp-cli -e 'structure src/'  # See architecture
rp-cli -e 'search "pattern" --max-results 20'  # Find related code

# Fast code search (Morph/WarpGrep)
uv run python -m runtime.harness scripts/morph_search.py --query "existing implementation" --path "."

# Fast code edits (Morph/Apply) - for implementation agents
uv run python -m runtime.harness scripts/morph_apply.py \
    --file "path/to/file.py" \
    --instruction "Description of change" \
    --code_edit "// ... existing code ...\nnew_code\n// ... existing code ..."

Step 4: Write Output

ALWAYS write your plan to:

$CLAUDE_PROJECT_DIR/.claude/cache/agents/plan-agent/output-{timestamp}.md

Also copy to persistent location if plan should survive cache cleanup:

$CLAUDE_PROJECT_DIR/thoughts/shared/plans/[descriptive-name].md

Read the full file on GitHub · 126 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. 4d ago First seen · 126 lines · 16 tokens per session scan A 8fe91a1fb43e

Subscribe to this mod's changes

plan-agent is an agent published in the GitHub repository parcadei/Continuous-Claude-v3 (3,934 stars, last pushed 7mo ago), licensed MIT. It adds 16 tokens to every session and 769 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.

Related

Other agents, from other repositories

fizzy-tasks

Lightweight agent for Fizzy.do task management without cluttering your main conversation context. Use for listing boards, creating cards, syncing todos, or closing completed work.

keskinonur/claude-plugin-fizzy · 39 tokens

e2e-test-agent

E2E test agent for validation.

alex-feel/claude-code-toolbox · 13 tokens

flutter-pm

Flutter Project Manager. Decomposes requirements into structured tasks. Maintains task registry (.tasks/REGISTRY.md) with history. Searches for similar past tasks. Creates test scenarios and Maestro E2E test cases for every task. Supports Asana task URLs as input.

aleksandr-chaika/flutter-clean-arch-skills · 58 tokens

maestro-tester

QE E2E testing agent for Flutter apps using Maestro. Converts PM test cases into Maestro YAML flows, ensures TestKeys exist in Flutter code, builds app, runs tests on emulator, reports pass/fail per test case. Use after unit/widget tests pass to verify user journeys.

aleksandr-chaika/flutter-clean-arch-skills · 63 tokens

flutter-dev

Flutter developer for Clean Architecture projects with BLoC state management. Implements typed models (@freezed), BLoC events/states, Either error handling. Use for all Flutter/Dart mobile implementation tasks.

aleksandr-chaika/flutter-clean-arch-skills · 45 tokens

flutter-tester

Flutter testing agent. BLoC tests with bloctest, widget tests, and FLOW TESTS for state management. Mocktail + MockBloc. 80%+ coverage target. CRITICAL: always includes flow tests for CRUD operations.

aleksandr-chaika/flutter-clean-arch-skills · 51 tokens