plan

plan is a command for Claude Code from Connectry-io/connectrylab-architect-cert-mcp. It costs 0 tokens per session (431 once invoked), scanned A, original, MIT.

A decision aid that evaluates whether a coding task needs a detailed plan or can be handled directly.

In plain words
What is it for?
It is for scoring task complexity, recommending plan mode or direct execution, and outlining implementation phases when a plan is needed.
Why use it?
It helps choose an appropriate level of preparation by considering files, dependencies, ambiguity, risk, and cross-cutting work.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Good fit It is for scoring task complexity, recommending plan mode or direct execution, and outlining implementation phases when a plan is needed.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/connectry-io/connectrylab-architect-cert-mcp/plan
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/Connectry-io/connectrylab-architect-cert-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/commands/connectry-io/connectrylab-architect-cert-mcp/plan/github.svg)](https://agentmods.dev/commands/connectry-io/connectrylab-architect-cert-mcp/plan)
Your own site
<a href="https://agentmods.dev/commands/connectry-io/connectrylab-architect-cert-mcp/plan"><img src="https://agentmods.dev/badge/commands/connectry-io/connectrylab-architect-cert-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/commands/connectry-io/connectrylab-architect-cert-mcp/plan"><img src="https://agentmods.dev/badge/commands/connectry-io/connectrylab-architect-cert-mcp/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 431 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.00000 $0.00431
Opus 5 $0.00000 $0.00216
Sonnet 5 $0.00000 $0.00086
Haiku 4.5 $0.00000 $0.00043

Measured 9d ago against content hash 330ee927e66a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, 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 9d 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.

projects/d3-config/.claude/commands/plan.md · 55 lines

What it actually says

Complexity Assessment — Plan or Execute?

Evaluate the requested task and recommend whether to use plan mode or direct execution.

Task Description

$ARGUMENTS

Assessment Heuristic

Score each dimension (0 = low, 1 = medium, 2 = high):

Dimension 0 (Direct) 1 (Either) 2 (Plan)
Files touched 1-2 files 3-5 files 6+ files
Cross-cutting Single module 2 modules 3+ modules
Ambiguity Clear spec Some unknowns Vague requirements
Risk Easily reversible Moderate impact Breaking change / data migration
Dependencies None Internal deps External API / schema changes

Total score interpretation:

  • 0-3: Direct execution. Task is well-scoped and low-risk.
  • 4-6: Use judgment. Plan if any single dimension scores 2.
  • 7-10: Plan mode recommended. Break into phases with checkpoints.

Output

  1. Score each dimension with justification
  2. Calculate total and state recommendation
  3. If plan mode: outline 3-5 implementation phases
  4. If direct mode: suggest the first concrete step

When to Override

Always use plan mode regardless of score when:

  • The task involves database schema changes
  • The task modifies authentication or authorization logic
  • The task affects the public API contract
  • The user explicitly requests a plan
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. 9d ago First seen · 55 lines · 0 tokens per session scan A 330ee927e66a

Subscribe to this mod's changes

plan is a command published in the GitHub repository Connectry-io/connectrylab-architect-cert-mcp (33 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 431 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.