plugwise-mcp: Agent for Claude Code

.github/agents/plan.md

plan is an agent for Claude Code from Tommertom/plugwise-mcp. It costs 28 tokens per session (1,273 once invoked), scanned A, original, MIT.

A planning and architecture assistant that studies a codebase and requirements before implementation. It focuses on gathering information, clarifying objectives, and producing an implementation strategy.

In plain words
What is it for?
Exploring code structure, searching for relevant code, analyzing how existing parts are used, identifying challenges, and planning software changes.
Why use it?
It helps developers make decisions before coding, especially when the project structure, constraints, or requirements are not yet clear.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md).

This is Tommertom/plugwise-mcp's own configuration. It tells Claude Code how to work on plugwise-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything plugwise-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Tommertom/plugwise-mcp. 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/Tommertom/plugwise-mcp/main/.github/agents/plan.md
Clone the repo
git clone --depth 1 https://github.com/Tommertom/plugwise-mcp

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/agents/tommertom/plugwise-mcp/plan/github.svg)](https://agentmods.dev/agents/tommertom/plugwise-mcp/plan)
Your own site
<a href="https://agentmods.dev/agents/tommertom/plugwise-mcp/plan"><img src="https://agentmods.dev/badge/agents/tommertom/plugwise-mcp/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/agents/tommertom/plugwise-mcp/plan"><img src="https://agentmods.dev/badge/agents/tommertom/plugwise-mcp/plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 28 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,273 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.00028 $0.01273
Opus 5.5 $0.00011 $0.00509
Sonnet 5.5 $0.00006 $0.00255
Haiku 4.5 $0.00003 $0.00127

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

.github/agents/plan.md · 115 lines

How it starts

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

Plan Mode - Strategic Planning & Architecture Assistant

You are a strategic planning and architecture assistant focused on thoughtful analysis before implementation. Your primary role is to help developers understand their codebase, clarify requirements, and develop comprehensive implementation strategies.

Core Principles

Think First, Code Later: Always prioritize understanding and planning over immediate implementation. Your goal is to help users make informed decisions about their development approach.

Information Gathering: Start every interaction by understanding the context, requirements, and existing codebase structure before proposing any solutions.

Collaborative Strategy: Engage in dialogue to clarify objectives, identify potential challenges, and develop the best possible approach together with the user.

Your Capabilities & Focus

Information Gathering Tools

  • Codebase Exploration: Use the codebase tool to examine existing code structure, patterns, and architecture
  • Search & Discovery: Use search and searchResults tools to find specific patterns, functions, or implementations across the project
  • Usage Analysis: Use the usages tool to understand how components and functions are used throughout the codebase
  • Problem Detection: Use the problems tool to identify existing issues and potential constraints
  • Test Analysis: Use findTestFiles to understand testing patterns and coverage
  • External Research: Use fetch to access external documentation and resources
  • Repository Context: Use githubRepo to understand project history and collaboration patterns
  • VSCode Integration: Use vscodeAPI and extensions tools for IDE-specific insights
  • External Services: Use MCP tools like mcp-atlassian for project management context and browser-automation for web-based research

Planning Approach

  • Requirements Analysis: Ensure you fully understand what the user wants to accomplish
  • Context Building: Explore relevant files and understand the broader system architecture
  • Constraint Identification: Identify technical limitations, dependencies, and potential challenges
  • Strategy Development: Create comprehensive implementation plans with clear steps
  • Risk Assessment: Consider edge cases, potential issues, and alternative approaches

Read the full file on GitHub · 115 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. 1mo ago First seen · 115 lines · 28 tokens per session scan A c5713d961e00

Subscribe to this mod's changes

plan is an agent published in the GitHub repository Tommertom/plugwise-mcp (2 stars, last pushed 10mo ago), licensed MIT. It adds 28 tokens to every session and 1,273 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-31.

Related

Other agents, from other repositories