Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
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.
[](https://agentmods.dev/skills/vcnoc/claude-code-zen-mcp-skill-work/plan-down)<a href="https://agentmods.dev/skills/vcnoc/claude-code-zen-mcp-skill-work/plan-down"><img src="https://agentmods.dev/badge/skills/vcnoc/claude-code-zen-mcp-skill-work/plan-down.svg" alt="Measured on agentmods" height="20"></a>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.00102 | $0.08971 |
| Opus 5 | $0.00051 | $0.04485 |
| Sonnet 5 | $0.00020 | $0.01794 |
| Haiku 4.5 | $0.00010 | $0.00897 |
Grade A, and why
plan-down 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.
How it starts
The opening of the file, as written. The whole thing — 1,034 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan-Down - Method-Driven Four-Path Intelligent Planning Generator
Overview
This skill provides a comprehensive method clarity-driven planning workflow that intelligently adapts to both user interaction preference (Interactive/Automatic) and implementation method clarity (Clear/Unclear).
Core Innovation: Uses zen-mcp chat as decision module to assess whether user provides a "clear implementation method" before planning.
Four Execution Paths:
- Interactive + Clear: Direct planning with user approval
- Interactive + Unclear: Multi-round dialogue to clarify method, then plan
- Automatic + Clear: Fully automated planning
- Automatic + Unclear: AI chain (clink → chat → consensus) to enrich method, then plan
The final output is a complete plan.md file ready for implementation.
Technical Architecture:
- zen-mcp chat: Method clarity judgment + interactive clarification + deep thinking (via clink)
- zen-mcp planner: Interactive, sequential planning tool with revision and branching capabilities
- zen-mcp consensus: Multi-model method validation (only for Automatic + Unclear path)
- Main Claude Model: Context gathering, workflow orchestration, plan.md generation
- User: Provides ideas/requirements (interactive mode) or none (automatic mode)
New Four-Path Workflow:
User Request → Phase 0 (chat: Method Clear?) → [Conditional Phase 1] → Phase 2 (planner) → Phase 3 (plan.md)
↓ ↓
Clear / Unclear Clear: Skip to Phase 2
Unclear: Phase 1 (Clarify/Enrich)
↓
Interactive: Dialogue with user
Automatic: clink → chat → consensus
Division of Responsibilities:
Phase 0 (Method Clarity Assessment - ALWAYS):
- chat tool: Judge if user provides clear implementation method
- Main Claude: Gather context from CLAUDE.md/PROJECTWIKI.md
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.
- 7d ago First seen · 1,034 lines · 102 tokens per session scan A 843e5d592e34
plan-down is a skill published in the GitHub repository VCnoC/Claude-Code-Zen-mcp-Skill-Work (116 stars, last pushed 8mo ago), licensed Apache-2.0. It adds 102 tokens to every session and 8,971 once invoked, about $0.0005 per session on Opus 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…