plan

A command for turning a defined piece of work into frontend and backend tasks, ordered by dependencies.

In plain words
What is it for?
Use it to plan full-stack changes, split responsibilities between frontend and backend, and define validation steps.
Why use it?
It makes the work sequence and the way each part will be checked clear before implementation starts.

Command for Claude Code

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.

agentmods
npx agentmods add commands/vaquarkhan/fullstack-development-agent-skills/plan
Clone the repo
git clone --depth 1 https://github.com/vaquarkhan/Fullstack-development-agent-skills

Made for: Claude Code.

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 18 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.00018
Opus 5 $0.00000 $0.00009
Sonnet 5 $0.00000 $0.00004
Haiku 4.5 $0.00000 $0.00002

Measured 2d ago against content hash da943de6fa7b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 2d 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 · 4 lines

What it actually says

/plan

Break scoped work into frontend/backend slices with dependency order and validation strategy.

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. 2d ago First seen · 4 lines · 0 tokens per session scan A da943de6fa7b

Subscribe to this mod's changes

plan is a command published in the GitHub repository vaquarkhan/Fullstack-development-agent-skills (2 stars, last pushed 18d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 18 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-31.