plan

plan is a skill for Claude Code from greglas75/zuvo. It costs 53 tokens per session (11,600 once invoked), scanned A, original, MIT.

A planning tool that turns an approved specification or a written request into ordered implementation tasks with tests and verification steps. TDD means writing a failing test before the code that makes it pass.

In plain words
What is it for?
Use it to analyze a project, choose implementation patterns, assess testability, and create TDD-based tasks with exact checks.
Why use it?
It gives developers a concrete sequence of work and connects each task to a requirement, reducing missed details.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: reads .claude/ paths; mentions subagents; mentions Claude Code.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is 1. ../../shared/includes/codesift-setup.md -- READ/MISSING.

Part of the zuvo plugin — 57 skills, 48 agents, 5 hooks shipped together

Good fit Use it to analyze a project, choose implementation patterns, assess testability, and create TDD-based tasks with exact checks.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/greglas75/zuvo
agentmods
npx agentmods add skills/greglas75/zuvo/plan

Made for: Claude Code.

Or install zuvo, the plugin that ships this one along with the rest of its 57 skills, 48 agents, 5 hooks.

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/skills/greglas75/zuvo/plan/github.svg)](https://agentmods.dev/skills/greglas75/zuvo/plan)
Your own site
<a href="https://agentmods.dev/skills/greglas75/zuvo/plan"><img src="https://agentmods.dev/badge/skills/greglas75/zuvo/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/skills/greglas75/zuvo/plan"><img src="https://agentmods.dev/badge/skills/greglas75/zuvo/plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 53 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 11,600 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. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 3 findings, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • high Prompt Injection · line 211
    Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
    Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
  • medium Agent Snooping · line 109
    Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
    Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
  • medium Rogue Agent · line 152
    Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
    Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
How audits are shown
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.00053 $0.11600
Opus 5.5 $0.00021 $0.04640
Sonnet 5.5 $0.00011 $0.02320
Haiku 4.5 $0.00005 $0.01160

Measured 7d ago against content hash 1597b3277e13, 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 7d 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.

skills/plan/SKILL.md · 681 lines

How it starts

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

zuvo:plan

Create a detailed, task-by-task implementation plan. Every task follows the TDD protocol: RED (failing test) -> GREEN (minimal code) -> Verify -> Commit.


Input Resolution

Determine the planning input. Two modes: spec-driven (from brainstorm output) or inline (from user description).

Step 1: Look for a spec

  1. If the user provided an explicit path (e.g., zuvo:plan docs/specs/my-spec.md), use that file
  2. Otherwise, search: Glob("docs/specs/*-spec.md")
  3. If multiple specs exist, present the list and ask the user which one to plan against

Step 2: Determine mode

  • Spec found with status: Approved → spec-driven mode. Read spec in full. This is the source of truth.
  • Spec found without status: Approved → Print: "Spec exists but is not approved. Using it as reference in inline mode." Treat spec as context, not authority. → inline mode.
  • No spec found → inline mode.

Inline mode requirements

The user's message (argument to zuvo:plan) IS the planning input. Extract:

  • Goal: what they want built
  • Scope: which files/areas are affected (explore codebase if not stated)
  • Constraints: any stated requirements

If the user's description is too vague to plan against (less than one sentence, no clear deliverable), ask ONE clarifying question. Do not block — a couple of sentences is enough to plan from.

Set planning_mode: "inline" or planning_mode: "spec-driven" — this affects the plan document header and review phase.


Artifact Detection

Check if a plan already exists:

  1. Glob("docs/specs/*-plan.md") — look for existing plans
  2. Spec-driven mode: match by spec_id field. If a matching plan exists, ask the user whether to revise or start fresh.
  3. Inline mode: skip this check (no spec_id to match against)
  4. If no plan exists, proceed to Phase 1

Mandatory File Loading

Phase 0 — Bootstrap (load before any work)

CORE FILES LOADED:
  1. ../../shared/includes/codesift-setup.md            -- READ/MISSING
  2. ../../shared/includes/env-compat.md                 -- READ/MISSING
  3. ../../shared/includes/quality-gates.md              -- READ/MISSING
  4. ../../shared/includes/tdd-protocol.md               -- READ/MISSING
  5. ../../shared/includes/session-state.md              -- READ/MISSING
  6. ../../shared/includes/acceptance-proof-protocol.md  -- READ/MISSING
  7. ../../shared/includes/provided-artifact-supremacy.md -- READ/MISSING
  8. ../../rules/file-limits.md                          -- READ/MISSING
  9. ../../shared/includes/run-logger.md                 -- DEFERRED (completion)
 10. ../../shared/includes/retrospective.md              -- DEFERRED (completion)

Read the full file on GitHub · 681 lines

Files

What ships with it

5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 7d ago Changed · +9 lines 1597b3277e13
  2. 9d ago Changed · +2 lines 7814d98b68f3
  3. 27d ago Changed · +7 lines 2c2ac0b1c391
  4. 1mo ago Changed 3a0598626424
  5. 1mo ago Changed · +1 lines 942f2b2ccea8
  6. 1mo ago First seen · 662 lines · 53 tokens per session scan A 172f322ab5b7

Subscribe to this mod's changes

plan is a skill published in the GitHub repository greglas75/zuvo (8 stars, last pushed yesterday), licensed MIT. It adds 53 tokens to every session and 11,600 once invoked, about $0.0002 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-09-03.

Related

Other skills, from other repositories

ring:running-dev-cycle

Running the backend dev cycle: implements every task in a rolling-wave plan.md (ring:writing-plans format) for a Go/TS service, driving specialist agents through Gate 0 implementation/TDD, Gate 8 parallel review, and Gate 9 validation per epic, elaborating later phases at each phase boundary. Use when starting or…

LerianStudio/ring · 122 tokens

ring:instrumenting-streaming-events

Instrumenting streaming events: wires lib-streaming event emission end-to-end into a Lerian Go service via a 13-gate cycle (catalog, Builder bootstrap, Emit sites, outbox, HTTP manifest, NoopEmitter fallback, integration and chaos tests), dispatching ring:backend-go under TDD. Consumes the validated…

LerianStudio/ring · 102 tokens

ring:implementing-tasks

Implementing a single planned task (Task N.M.T) end-to-end: selects the right backend agent by language and service type, drives one TDD RED->GREEN turn, then verifies coverage, lint, license headers, runtime, and delivery before handoff. Runs as Gate 0 before ring:reviewing-code. Use to drive ONE task inside an…

LerianStudio/ring · 103 tokens

refactor

You are the Refactor Specialist, a rigorous code quality engineer who improves code structure, maintainability, and performance while preserving behavior. You never break working code - you make it better.

samibs/skillfoundry · 6 tokens

ai-agent-bench

Compare Claude Code and Codex on the same code task, with isolated worktrees, common checks, time, and cost.

reidemeister94/development-skills · 30 tokens

engineering-craft

Use when writing or changing any production code or tests — new features, bug fixes, refactors, or test authoring, in any language, by any model on any CLI.

mickeyyaya/evolve-loop · 40 tokens