vmark: Skill for Claude Code

.claude/skills/planning/SKILL.md

planning is a skill for Claude Code from xiaolai/vmark. It costs 38 tokens per session (1,193 once invoked), scanned A, original, ISC.

A planning tool that turns a software task into a documented implementation plan.

In plain words
What is it for?
Use it for roadmaps, specifications, migrations, API changes, performance-sensitive work, and other multi-step tasks.
Why use it?
It helps clarify requirements, decisions, dependencies, current behavior, tests, and acceptance conditions before coding.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

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

Reuse

Borrowing it

Nothing to install: this file belongs to xiaolai/vmark. 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/xiaolai/vmark/main/.claude/skills/planning/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/xiaolai/vmark

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 planning

README.md
[![agentmods](https://agentmods.dev/badge/skills/xiaolai/vmark/planning/github.svg)](https://agentmods.dev/skills/xiaolai/vmark/planning)
Your own site
<a href="https://agentmods.dev/skills/xiaolai/vmark/planning"><img src="https://agentmods.dev/badge/skills/xiaolai/vmark/planning/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 planning

Your own site · 80×15
<a href="https://agentmods.dev/skills/xiaolai/vmark/planning"><img src="https://agentmods.dev/badge/skills/xiaolai/vmark/planning.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,193 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 pass 7 Sept 2026
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.00038 $0.01193
Opus 5.5 $0.00015 $0.00477
Sonnet 5.5 $0.00008 $0.00239
Haiku 4.5 $0.00004 $0.00119

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

Security

Grade A, and why

planning 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/skills/planning/SKILL.md · 131 lines

How it starts

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

Planning Skill

When to use

Use this skill when the user asks for planning, a roadmap, a spec-to-implementation breakdown, or wants decisions documented.

Modes

Choose the lightest mode that meets the request.

quick-plan

Use when:

  • task is small/medium and non-breaking
  • no migrations and no multi-phase rollout

Output:

  • 3–8 Work Items (WI-###), each with tests + acceptance

full-plan (default)

Use when:

  • migrations/persistence changes
  • API/contract changes (public tools, schemas, SDKs)
  • multi-phase roadmaps
  • performance-sensitive work

Output:

  • structured plan sections (see “Plan file template”)

Process

  1. Clarify outcomes

    • Restate desired behaviors and constraints.
    • Identify ambiguities and propose defaults if the user doesn’t decide.
    • Capture constraints & dependencies (runtime versions, OS, external services, feature flags, required tools).
    • Capture gaps: list requirement/behavior gaps or missing decisions revealed here.
  2. Inventory current behavior

    • Trace entry points → state/store → side effects → persistence.
    • List key files/modules and the invariants they rely on.
    • Note ownership/priority rules (windows, workspaces, files).
    • Capture gaps: list where current behavior diverges from the stated outcomes.
  3. Define target rules

    • Convert outcomes into explicit rules and precedence.
    • For each rule, include: trigger/context, expected behavior, scope, constraints, and exclusions.
    • Edge-case pass: cover empty/none, invalid/malformed, boundary sizes, conflicting state, multi-surface coordination, persistence/restore, and I/O failures.
    • Capture gaps: list rules that lack implementation support or current behavior conflicts.
    • Create a Decision Log:
      • decision, options considered, rationale, and why alternatives were rejected.
    • Create an Open Questions list:
      • questions that block correctness, who decides, and what the default is if not decided.

Read the full file on GitHub · 131 lines

Files

What ships with it

1 file 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. 2mo ago First seen · 131 lines · 38 tokens per session scan A eaa5bbe9faa4

Subscribe to this mod's changes

planning is a skill published in the GitHub repository xiaolai/vmark (878 stars, last pushed yesterday), licensed ISC. It adds 38 tokens to every session and 1,193 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-08-30.

Related

Other skills, from other repositories

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…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens