A command that turns a PRD—a document describing product requirements—into a detailed technical work plan for an existing codebase. It maps requirements to specific files, components, and tasks.

Use it to inspect the codebase, connect planned features to existing architecture and patterns, define file-level tasks and implementation notes, and save them in tasks.md.

It removes the guesswork between product requirements and implementation. You get an engineering roadmap before any code is changed.

How that0n3guy/mealie-mcp-server-ts configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to that0n3guy/mealie-mcp-server-ts. 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/that0n3guy/mealie-mcp-server-ts/main/.claude/commands/clavix/plan.md

Clone the repo

git clone --depth 1 https://github.com/that0n3guy/mealie-mcp-server-ts

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/that0n3guy/mealie-mcp-server-ts/plan/github.svg)](https://agentmods.dev/commands/that0n3guy/mealie-mcp-server-ts/plan)

Your own site

<a href="https://agentmods.dev/commands/that0n3guy/mealie-mcp-server-ts/plan"><img src="https://agentmods.dev/badge/commands/that0n3guy/mealie-mcp-server-ts/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/that0n3guy/mealie-mcp-server-ts/plan"><img src="https://agentmods.dev/badge/commands/that0n3guy/mealie-mcp-server-ts/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 7,524 The whole file, excluding the scripts and references it only reads on demand.

Security scan B 1 finding. 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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.07524
Opus 5.5	$0.00000	$0.03010
Sonnet 5.5	$0.00000	$0.01505
Haiku 4.5	$0.00000	$0.00752

Measured 2mo ago against content hash cf00daddeadf, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade B, and why

plan scanned grade B with 1 finding 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.

Subtle steeringmediumPrompt injection

Instructions that bias recommendations or shape behaviour without the user noticing.

**⚠️ Never tell the user a file was saved without verifying it exists.**

.claude/commands/clavix/plan.md · 969 lines

How it starts

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

Clavix: Plan Your Implementation

I'll turn your PRD into a low-level, technically detailed implementation plan that fits your existing codebase.

What This Does

When you run /clavix:plan, I:

Analyze your Codebase - Understand your existing architecture, patterns, and stack
Read your PRD - Understand new requirements
Bridge the Gap - Map requirements to specific files and existing components
Generate Technical Tasks - detailed, file-specific instructions
Create tasks.md - Your comprehensive engineering roadmap

I create the plan. I don't build anything yet.

CLAVIX MODE: Technical Planning

I'm in planning mode. Creating your engineering roadmap.

What I'll do:

✓ Analyze existing code structure & patterns
✓ Map PRD features to specific technical implementations
✓ Define exact file paths and signatures
✓ Create "Implementation Notes" for each task
✓ Save tasks.md for implementation

What I won't do:

✗ Write any code yet
✗ Start implementing features
✗ Create actual components

I'm planning strictly how to build it.

For complete mode documentation, see: .clavix/instructions/core/clavix-mode.md

Self-Correction Protocol

DETECT: If you find yourself doing any of these mistake types:

Type	What It Looks Like
1. Generic Tasks	"Create login page" (without specifying file path, library, or pattern)
2. Ignoring Context	Planning a Redux store when the project uses Zustand, or creating new CSS files when Tailwind is configured
3. Implementation Code	Writing full function bodies or components during the planning phase
4. Missing Task IDs	Not assigning proper task IDs for tracking
5. Capability Hallucination	Claiming features Clavix doesn't have

STOP: Immediately halt the incorrect action.

CORRECT: Output: "I apologize - I was [describe mistake]. Let me return to generating specific technical tasks based on the codebase."

Read the full file on GitHub · 969 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.

2mo ago First seen · 969 lines · 0 tokens per session scan B cf00daddeadf

Subscribe to this mod's changes

plan is a command published in the GitHub repository that0n3guy/mealie-mcp-server-ts (0 stars, last pushed 10mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 7,524 tokens. A static security scan graded it B with 1 finding (subtle steering). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Planning

plan next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
planthat0n3guy/mealie-mcp-server-ts	Command	0	10mo ago	MIT	B	0	Claude Code
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	yesterday	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	yesterday	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	yesterday	MIT	A	14	Claude Code

mealie-mcp-server-ts: Command for Claude Code