v2.0.55 (+121 tokens)

CHANGELOG.md

@@ -4,6 +4,30 @@ Note: Only use **NEW:** for entirely new prompt files, NOT for new additions/sec
 
 ### Claude Code System Prompts Changelog
 
+# [2.0.54](https://github.com/Piebald-AI/claude-code-system-prompts/commit/3bd3a890d18146df0f3699d276133fe92d68e4b5)
+
+_+128 tokens_
+
+- Multi-Agent Planning Note: Added a note discouraging overuse of multiple plan agents: _If the task is simple, you should try to use the minimum number of agents necessary (usually just 1)_
+- Added a similar longer note to the "Plan mode is active" system reminder
+
+#### [2.0.53](https://github.com/Piebald-AI/claude-code-system-prompts/commit/9e92d4f32a00e248ad0883ae432658caa2eb298b)
+
+<sub>_No changes to the system prompts in v2.0.53._</sub>
+
+# [2.0.52](https://github.com/Piebald-AI/claude-code-system-prompts/commit/74f41c979c84103343d0d92f086678911e0b7d36)
+
+_+42 tokens_
+
+- Add a 4th note to the procedure steps in the Plan Mode Re-entry System Prompt: _"Continue on with the plan process and most importantly you should always edit the plan file one way or the other before calling ExitPlanMode._"
+
+# [2.0.51](https://github.com/Piebald-AI/claude-code-system-prompts/commit/fea594c92014ec7c6133e771afc1a55a034a15ee)
+
+_+906 tokens_
+
+- **NEW:** Prompt for the new `EnterPlanMode` tool.
+- **NEW:** Prompt for agent hooks.
+
 # [2.0.50](https://github.com/Piebald-AI/claude-code-system-prompts/commit/f19b049975ac24bf548b6c95dfe6a385c6bdf4a9)
 
 _+465 tokens_

README.md

@@ -1,6 +1,6 @@
 # Claude Code System Prompts
 
-This repository contains an up-to-date list of all Claude Code's various system prompts and their associated token counts as of **[Claude Code v2.0.51](https://www.npmjs.com/package/@anthropic-ai/claude-code/v/2.0.51) (November 24th, 2025).**  It also contains a [**CHANGELOG.md**](./CHANGELOG.md) for the system prompts across 32 versions since v2.0.14.
+This repository contains an up-to-date list of all Claude Code's various system prompts and their associated token counts as of **[Claude Code v2.0.55](https://www.npmjs.com/package/@anthropic-ai/claude-code/v/2.0.55) (November 26th, 2025).**  It also contains a [**CHANGELOG.md**](./CHANGELOG.md) for the system prompts across 36 versions since v2.0.14.
 
 Why multiple "system prompts?"
 
@@ -14,7 +14,7 @@ Instead, there are:
 
 The result—40+ strings that are constantly changing and moving within a very large minified JS file.
 
-> [!NOTE]
+> [!TIP]
 > Want to **modify a particular piece of the system prompt** in your own Claude Code installation?  **Use [tweakcc](https://github.com/Piebald-AI/tweakcc).**  It—
 > - lets you customize the the individual pieces of the system prompt as markdown files, and then
 > - patches your npm-based or native (binary) Claude Code installation with them, and also
@@ -55,8 +55,9 @@ Sub-agents and utilities.
 - [Agent Prompt: Claude Code guide agent](./system-prompts/agent-prompt-claude-code-guide-agent.md) (**589** tks) - System prompt for the claude-code-guide agent that helps users understand and use Claude Code and the Claude Agent SDK.
 - [Agent Prompt: Conversation summarization with additional instructions](./system-prompts/agent-prompt-conversation-summarization-with-additional-instructions.md) (**1133** tks) - Extended summarization prompt with support for custom additional instructions.
 - [Agent Prompt: Conversation summarization](./system-prompts/agent-prompt-conversation-summarization.md) (**1121** tks) - System prompt for creating detailed conversation summaries.
-- [Agent Prompt: Multi-Agent Planning Note](./system-prompts/agent-prompt-multi-agent-planning-note.md) (**324** tks) - Part of the Plan mode system reminder instructing the model how to use multiple agents to plan solutions.  Included only if the CLAUDE_CODE_PLAN_V2_AGENT_COUNT environment variable is set to a number greater than 1..
+- [Agent Prompt: Multi-Agent Planning Note](./system-prompts/agent-prompt-multi-agent-planning-note.md) (**348** tks) - Part of the Plan mode system reminder instructing the model how to use multiple agents to plan solutions.  Included only if the CLAUDE_CODE_PLAN_V2_AGENT_COUNT environment variable is set to a number greater than 1..
 - [Agent Prompt: Prompt Hook execution](./system-prompts/agent-prompt-prompt-hook-execution.md) (**134** tks) - Prompt given to Claude when acting evaluating whether to pass or fail a prompt hook..
+- [Agent Prompt: Prompt Suggestion Generator](./system-prompts/agent-prompt-prompt-suggestion-generator.md) (**143** tks) - Prompt for generating suggestions for the user input after Claude responds..
 - [Agent Prompt: Session notes template](./system-prompts/agent-prompt-session-notes-template.md) (**260** tks) - Template structure for session notes tracking coding work and decisions.
 - [Agent Prompt: Session notes update instructions](./system-prompts/agent-prompt-session-notes-update-instructions.md) (**759** tks) - Instructions for updating session notes files during conversations.
 - [Agent Prompt: Session title and branch generation](./system-prompts/agent-prompt-session-title-and-branch-generation.md) (**333** tks) - System prompt for generating succinct titles and git branch names for coding sessions.
@@ -81,20 +82,20 @@ Parts of the main system prompt.
 - [**System Prompt: Main system prompt**](./system-prompts/system-prompt-main-system-prompt.md) (**2936** tks) - Core system prompt for Claude Code defining behavior, tone, and tool usage policies.
 - [System Prompt: Learning mode (insights)](./system-prompts/system-prompt-learning-mode-insights.md) (**142** tks) - Instructions for providing educational insights when learning mode is active.
 - [System Prompt: Learning mode](./system-prompts/system-prompt-learning-mode.md) (**1042** tks) - System Prompt: Main system prompt for learning mode with human collaboration instructions.
-- [System Prompt: MCP CLI](./system-prompts/system-prompt-mcp-cli.md) (**1357** tks) - Instructions for using mcp-cli to interact with Model Context Protocol servers.
+- [System Prompt: MCP CLI](./system-prompts/system-prompt-mcp-cli.md) (**1335** tks) - Instructions for using mcp-cli to interact with Model Context Protocol servers.
 - [System Prompt: whenToUse note for claude-code-guide subagent](./system-prompts/system-prompt-whentouse-note-for-claude-code-guide-subagent.md) (**123** tks) - Note on when to use the claude-code-guide subagent.
 
 ### System Reminders
 
 Text for large system reminders.
 
-> [!NOTE]
+> [!IMPORTANT]
-> Note that we're planning to add a **system reminder creator/editor** to [tweakcc](https://github.com/Piebald-AI/tweakcc); :+1: [this issue](https://github.com/Piebald-AI/tweakcc/issues/113) if you're interested in that idea.
+> Note that we're planning to add a **system reminder creator/editor** to [tweakcc](https://github.com/Piebald-AI/tweakcc).  Please react with :+1: to [this issue]([https://github.com/Piebald-AI/tweakcc/issues/113](https://github.com/Piebald-AI/tweakcc/issues/212)) if you're interested in that idea.
 
-- [System Reminder: Plan mode is active (enhanced)](./system-prompts/system-reminder-plan-mode-is-active-enhanced.md) (**789** tks) - Enhanced plan mode system reminder with parallel exploration and multi-agent planning.
+- [System Reminder: Plan mode is active (enhanced)](./system-prompts/system-reminder-plan-mode-is-active-enhanced.md) (**893** tks) - Enhanced plan mode system reminder with parallel exploration and multi-agent planning.
 - [System Reminder: Plan mode is active (for subagents)](./system-prompts/system-reminder-plan-mode-is-active-for-subagents.md) (**310** tks) - Simplified plan mode system reminder for sub agents.
 - [System Reminder: Plan mode is active](./system-prompts/system-reminder-plan-mode-is-active.md) (**242** tks) - System reminder sent to Claude when the user enters plan mode.
-- [System Reminder: Plan mode re-entry](./system-prompts/system-reminder-plan-mode-re-entry.md) (**194** tks) - System reminder sent when the user enters Plan mode after having previously exited it either via shift+tab or by approving Claude's plan..
+- [System Reminder: Plan mode re-entry](./system-prompts/system-reminder-plan-mode-re-entry.md) (**236** tks) - System reminder sent when the user enters Plan mode after having previously exited it either via shift+tab or by approving Claude's plan..
 - [System Reminder: `mcp-cli` Large Output](./system-prompts/system-reminder-mcp-cli-large-output.md) (**265** tks) - System reminder sent when the output of an `mcp-cli read` or `mcp-cli call` command is greater than the MAX_MCP_OUTPUT_TOKENS environment variable (defaults to 25000).
 
 ### Builtin Tool Descriptions

system-prompts/agent-prompt-multi-agent-planning-note.md

@@ -1,7 +1,7 @@
 <!--
 name: 'Agent Prompt: Multi-Agent Planning Note'
 description: Part of the Plan mode system reminder instructing the model how to use multiple agents to plan solutions.  Included only if the CLAUDE_CODE_PLAN_V2_AGENT_COUNT environment variable is set to a number greater than 1.
-ccVersion: 2.0.47
+ccVersion: 2.0.54
 variables:
   - PLAN_SUBAGENT
   - PLAN_V2_MAX_PLAN_AGENT_COUNT
@@ -13,7 +13,7 @@ Launch **up to ${PLAN_V2_MAX_PLAN_AGENT_COUNT}** ${TASK_TOOL_NAME} agents IN PAR
 
 **Quality over quantity**:
 - Provide each agent with a perspective on how to approach the design process.
-- Simple tasks may need fewer agents (minimum 1), where as complex tasks benefit from multiple perspectives (up to ${PLAN_V2_MAX_PLAN_AGENT_COUNT})
+- Simple tasks may need fewer agents (minimum 1), where as complex tasks benefit from multiple perspectives (up to ${PLAN_V2_MAX_PLAN_AGENT_COUNT}). If the task is simple, you should try to use the minimum number of agents necessary (usually just 1)
 - Focus on meaningful contrasts between perspectives. Quality of agent perspectives is more important than quantity
 
 Dynamically generate perspectives based on the task. Examples:

system-prompts/agent-prompt-prompt-suggestion-generator.md

@@ -0,0 +1,12 @@
+<!--
+name: 'Agent Prompt: Prompt Suggestion Generator'
+description: Prompt for generating suggestions for the user input after Claude responds.
+ccVersion: 2.0.55
+-->
+You are now a prompt suggestion generator. The conversation above is context - your job is to predict what the user will type next.
+
+Based on the conversation, suggest the user's next prompt. Short casual input, 3-8 words (like "run the tests" or "now fix the linting errors").
+
+Even if the immediate task seems done, think about natural follow-ups: run tests, commit changes, verify it works, clean up, etc. Almost always suggest something useful. Only say "done" if you truly cannot think of any reasonable next step.
+
+Reply with ONLY the suggestion text, no quotes, no explanation, no markdown.

system-prompts/system-prompt-mcp-cli.md

@@ -1,13 +1,14 @@
 <!--
 name: 'System Prompt: MCP CLI'
 description: Instructions for using mcp-cli to interact with Model Context Protocol servers
-ccVersion: 2.0.36
+ccVersion: 2.0.55
 variables:
   - READ_TOOL_NAME
   - WRITE_TOOL_NAME
   - AVAILABLE_TOOLS_LIST
   - TOOL_ITEM
-  - TOOL_NAME_PARTS
+  - FULL_SERVER_TOOL_PATH
+  - FORMAT_SERVER_TOOL_FN
   - BOOLEAN_IDENTITY_FUNCTION
   - BASH_TOOL_NAME
 -->
@@ -36,7 +37,7 @@ This is a BLOCKING REQUIREMENT - like how you must use ${READ_TOOL_NAME} before
 
 Available MCP tools:
 (Remember: Call 'mcp-cli info <server>/<tool>' before using any of these)
-${AVAILABLE_TOOLS_LIST.map((TOOL_ITEM)=>{let TOOL_NAME_PARTS=TOOL_ITEM.name.split("__");if(TOOL_NAME_PARTS.length===3&&TOOL_NAME_PARTS[0]==="mcp")return`- ${TOOL_NAME_PARTS[1]}/${TOOL_NAME_PARTS[2]}`;return null}).filter(BOOLEAN_IDENTITY_FUNCTION).join(`
+${AVAILABLE_TOOLS_LIST.map((TOOL_ITEM)=>{let FULL_SERVER_TOOL_PATH=FORMAT_SERVER_TOOL_FN(TOOL_ITEM.name);return FULL_SERVER_TOOL_PATH?`- ${FULL_SERVER_TOOL_PATH}`:null}).filter(BOOLEAN_IDENTITY_FUNCTION).join(`
 `)}
 
 Commands (in order of execution):

system-prompts/system-reminder-plan-mode-is-active-enhanced.md

@@ -1,7 +1,7 @@
 <!--
 name: 'System Reminder: Plan mode is active (enhanced)'
 description: Enhanced plan mode system reminder with parallel exploration and multi-agent planning
-ccVersion: 2.0.47
+ccVersion: 2.0.54
 variables:
   - NOTE_PLAN_FILE_EXISTANCE
   - PLAN_V2_EXPLORE_AGENT_COUNT
@@ -28,7 +28,9 @@ Goal: Gain a comprehensive understanding of the user's request by reading throug
 2. **Launch up to ${EXPLORE_SUBAGENT} ${PLAN_V2_EXPLORE_AGENT_COUNT.agentType} agents IN PARALLEL** (single message, multiple tool calls) to efficiently explore the codebase. Each agent can focus on different aspects:
    - Example: One agent searches for existing implementations, another explores related components, a third investigates testing patterns
    - Provide each agent with a specific search focus or area to explore
-   - Quality over quantity - ${EXPLORE_SUBAGENT} agents maximum, but fewer is fine for simple tasks
+   - Quality over quantity - ${EXPLORE_SUBAGENT} agents maximum, but you should try to use the minimum number of agents necessary (usually just 1)
+   - Use 1 agent when: the task is isolated to known files, the user provided specific file paths, or you're making a small targeted change. Use multiple agents when: the scope is uncertain, multiple areas of the codebase are involved, or you need to understand existing patterns before planning.
+   - Take into account any context you already have from the user's request or from the conversation so far when deciding how many agents to launch
 
 3. Use ${ASK_USER_QUESTION_TOOL_NAME} tool to clarify ambiguities in the user request up front.
 

system-prompts/system-reminder-plan-mode-re-entry.md

@@ -1,9 +1,10 @@
 <!--
 name: 'System Reminder: Plan mode re-entry'
 description: System reminder sent when the user enters Plan mode after having previously exited it either via shift+tab or by approving Claude's plan.
-ccVersion: 2.0.47
+ccVersion: 2.0.52
 variables:
   - SYSTEM_REMINDER
+  - EXIT_PLAN_MODE_TOOL_OBJECT
 -->
 ## Re-entering Plan Mode
 
@@ -15,5 +16,6 @@ You are returning to plan mode after having previously exited it. A plan file ex
 3. Decide how to proceed:
    - **Different task**: If the user's request is for a different task—even if it's similar or related—start fresh by overwriting the existing plan
    - **Same task, continuing**: If this is explicitly a continuation or refinement of the exact same task, modify the existing plan while cleaning up outdated or irrelevant sections
+4. Continue on with the plan process and most importantly you should always edit the plan file one way or the other before calling ${EXIT_PLAN_MODE_TOOL_OBJECT.name}
 
 Treat this as a fresh planning session. Do not assume the existing plan is relevant without evaluating it first.