agentmods.dev

wf-plan

wf-plan is a skill for Claude Code, Codex from marchatton/agent-skills. It costs 57 tokens per session (611 once invoked), scanned A, original, MIT.

A planning guide for turning an already-defined project brief, design notes, and risk assessment into a development plan.

In plain words
What is it for?
Writing a commit-ready plan for a project, including research, dependencies, rollout and rollback steps, observability, and verification.
Why use it?
It gives developers a shared implementation sequence, scope, acceptance checks, risks, and handoff points before coding begins.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

not rated 5repo 6mo ago A scan 57 tokens original MIT

Good fit Writing a commit-ready plan for a project, including research, dependencies, rollout and rollback steps, observability, and verification.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/marchatton/agent-skills/wf-plan
View source ↗ marchatton/agent-skills marchatton.com
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.

Any agent
npx skills add marchatton/agent-skills --skill wf-plan
Clone the repo
git clone --depth 1 https://github.com/marchatton/agent-skills

Made for: Claude Code, Codex.

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 wf-plan

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/marchatton/agent-skills/wf-plan"><img src="https://agentmods.dev/badge/skills/marchatton/agent-skills/wf-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 57 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 611 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.
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.00057 $0.00611
Opus 5 $0.00028 $0.00305
Sonnet 5 $0.00011 $0.00122
Haiku 4.5 $0.00006 $0.00061

Measured 9d ago against content hash 66b5a2c5c200, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

wf-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 9d 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.

.agents/skills/03-plan/wf-plan/SKILL.md · 88 lines

How it starts

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

wf-plan

Purpose

Turn a shaped packet (wf-shape dossier) into a commit-ready plan without re-litigating the shape.

Never implement production code. Only research and write the plan.

Inputs

Dossier folder path containing:

  • brief.md
  • breadboard-pack.md
  • risk-register.md
  • spike-investigation.md (if present)

Outputs

Inside the same dossier:

  • plan.md

Steps

  1. Pickup (recommended if new thread)
  • Invoke pickup if repo/branch state is not fresh.
  1. Ingest shaped packet (no idea refinement loop)
  • Read brief → breadboard → risk register → spikes.
  • If perimeter or top risks are missing: route back to wf-shape.
  1. Create plan skeleton
  • Create plan.md with:
    • scope (in/out)
    • key flows + key logic
    • acceptance criteria + verification plan
    • sequencing/phases + stop points
    • rollout/rollback + observability
    • dependencies + risks
  1. Local research (always)
  • Find similar patterns in repo.
  • Pull institutional learnings (docs/solutions, docs/LEARNINGS.md).
  • Record concrete file paths.
  1. External research (conditional)
  • Always external for: security/auth, payments, privacy, external APIs, migrations.
  • Otherwise only if local context is thin.
  1. Spec hardening (gap pass)
  • Edge cases, failure modes, concurrency, performance, data integrity, security threats.
  • Update acceptance criteria + verification.
  1. Plan review passes
  • Simplicity, risk, ops/release, data integrity, security/privacy, UX/product.
  • Final mandatory pass: invoke oracle on the whole plan and integrate findings (or mark out-of-bounds).
  1. Commit gate
  • GO only if:
    • AC measurable
    • verification per AC
    • sequencing explicit
    • rollout/rollback explicit
    • no P1 unknowns remain
  1. Handoff to build (recommended boundary)
  • Invoke handoff and include:
    • plan path + summary of phases
    • how to verify
    • rollout notes
    • biggest remaining risks
  • Recommend build in a fresh thread:
    • /new then pickup then run wf-develop or wf-ralph

Read the full file on GitHub · 88 lines

Files

What ships with it

2 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. 9d ago First seen · 88 lines · 57 tokens per session scan A 66b5a2c5c200

Subscribe to this mod's changes

wf-plan is a skill published in the GitHub repository marchatton/agent-skills (5 stars, last pushed 6mo ago), licensed MIT. It adds 57 tokens to every session and 611 once invoked, about $0.0003 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-31.

Planning
Related

Other skills, from other repositories

systematic-debugging

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

obra/superpowers · 21 tokens

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

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

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

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

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…

vercel/next.js · 103 tokens