agentmods.dev

markdown-vdb: Command for Claude Code

.claude/commands/plan.md

plan is a command for Claude Code from geckse/markdown-vdb. It costs 0 tokens per session (381 once invoked), scanned A, original, MIT.

A command that turns a feature request into a structured implementation plan after examining the codebase. An implementation plan describes the files, decisions, steps, and tests needed for the work.

In plain words
What is it for?
Use it to research the project, ask requirement questions, and document files to modify, files to create, implementation steps, and testing.
Why use it?
It helps break an unfamiliar coding task into concrete work and identifies important requirements before changes begin.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: mentions CLAUDE.md; names the AskUserQuestion tool.

This is geckse/markdown-vdb's own configuration. It tells Claude Code how to work on markdown-vdb 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 markdown-vdb configures →

not rated 29repo 2mo ago A scan 0 tokens original MIT
View source ↗ geckse/markdown-vdb
Reuse

Borrowing it

Nothing to install: this file belongs to geckse/markdown-vdb. 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/geckse/markdown-vdb/main/.claude/commands/plan.md
Clone the repo
git clone --depth 1 https://github.com/geckse/markdown-vdb

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/geckse/markdown-vdb/plan/github.svg)](https://agentmods.dev/commands/geckse/markdown-vdb/plan)
Your own site
<a href="https://agentmods.dev/commands/geckse/markdown-vdb/plan"><img src="https://agentmods.dev/badge/commands/geckse/markdown-vdb/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/geckse/markdown-vdb/plan"><img src="https://agentmods.dev/badge/commands/geckse/markdown-vdb/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 381 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.00381
Opus 5.5 $0.00000 $0.00152
Sonnet 5.5 $0.00000 $0.00076
Haiku 4.5 $0.00000 $0.00038

Measured 2mo ago against content hash 9495081a5a3f, 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 2mo 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/commands/plan.md · 38 lines

What it actually says

Plan: Create a Structured Implementation Plan

Take the following feature description and create a comprehensive, structured implementation plan.

Feature: $ARGUMENTS

Process

  1. Understand the request — Parse the feature description above. Identify what needs to change and what stays the same.

  2. Research the codebase — Read relevant source files to understand current patterns. Check existing code for conventions, architecture, and testing patterns. Read CLAUDE.md for project context.

  3. Ask clarifying questions — IMPORTANT: Before writing the plan, use the AskUserQuestion tool to ask at least 5 questions about requirements, edge cases, and design decisions. Cover: scope boundaries, error handling, backward compatibility, testing expectations, and UI/UX decisions. Provide suggested answers based on your codebase research.

  4. Write the plan — After receiving answers, create a structured plan with these sections:

    Summary

    One-paragraph description of what will be built.

    Files to Modify

    List every file that needs changes, with a description of what changes.

    Files to Create

    List any new files, with their purpose.

    Implementation Steps

    Numbered steps in implementation order. Each step should reference specific files and describe the exact changes.

    Testing Plan

    Which existing tests need updating, what new tests to write, and how to verify the feature end-to-end.

    Patterns to Follow

    Reference specific patterns from the existing codebase that the implementation should match.

  5. Save the plan — Write the plan to docs/plans/$ARGUMENTS.md (kebab-case the arguments). Create the docs/plans/ directory if it doesn't exist.

The plan should be detailed enough that a fresh Claude session with only the plan as input could implement the feature correctly.

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. 2mo ago First seen · 38 lines · 0 tokens per session scan A 9495081a5a3f

Subscribe to this mod's changes

plan is a command published in the GitHub repository geckse/markdown-vdb (29 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 381 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.

Planningclifilesystemmarkdownvector-database
Related

plan compared with commands from other repositories

plan next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
plangeckse/markdown-vdbCommand292mo agoMITA0Claude Code
landing-publishseite-sh/seiteCommand28yesterdayMITA0Claude Code
searchedochi/mdvsCommand2717d agoMITA0Claude Code
infoedochi/mdvsCommand2717d agoMITA0Claude Code
updateedochi/mdvsCommand2717d agoMITA0Claude Code
cleanedochi/mdvsCommand2717d agoMITA0Claude Code
export-jsonschemaedochi/mdvsCommand2717d agoMITA0Claude Code