agentmods.dev

planning-with-files

planning-with-files is a skill for Claude Code from MuduiClaw/ClawKing. It costs 56 tokens per session (1,447 once invoked), scanned A, a copy of planning-with-files, MIT.

A file-based planning method for complex, multi-step tasks. It keeps plans, findings, and progress in Markdown files in the project.

In plain words
What is it for?
Use it for research projects and tasks requiring more than five tool calls, with files such as task_plan.md, findings.md, and progress.md.
Why use it?
It preserves working context outside the chat, making long tasks easier to resume after a session is cleared and reducing the chance of losing decisions or discoveries.

Skill for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable. Also seen: names the TodoWrite tool.

Runs only inside a plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else, and the catalogue could not identify which plugin ships it.

not rated 11repo 4mo ago A scan 56 tokens copy · 78% MIT

Good fit Use it for research projects and tasks requiring more than five tool calls, with files such as task_plan.md, findings.md, and progress.md.

Compare 6 skills from other repositories ↓
View source ↗ MuduiClaw/ClawKing
Install

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.

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-with-files

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/muduiclaw/clawking/planning-with-files"><img src="https://agentmods.dev/badge/skills/muduiclaw/clawking/planning-with-files.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,447 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 78% copy Near-identical to another mod 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.00056 $0.01447
Opus 5 $0.00028 $0.00724
Sonnet 5 $0.00011 $0.00289
Haiku 4.5 $0.00006 $0.00145

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

Security

Grade A, and why

planning-with-files 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 10d ago.

The scan reads SKILL.md. This mod also ships 4 executable files (scripts/check-complete.ps1, scripts/check-complete.sh, scripts/init-session.ps1, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Origin

This is a copy

78% identical to planning-with-files — 69 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

workspace/skills/planning-with-files/SKILL.md · 186 lines

How it starts

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

Planning with Files

Work like Manus: Use persistent markdown files as your "working memory on disk."

FIRST: Check for Previous Session (v2.2.0)

Before starting work, check for unsynced context from a previous session:

# Linux/macOS
$(command -v python3 || command -v python) ${CLAUDE_PLUGIN_ROOT}/scripts/session-catchup.py "$(pwd)"

# Windows PowerShell
& (Get-Command python -ErrorAction SilentlyContinue).Source "$env:USERPROFILE\.claude\skills\planning-with-files\scripts\session-catchup.py" (Get-Location)

If catchup report shows unsynced context:

  1. Run git diff --stat to see actual code changes
  2. Read current planning files
  3. Update planning files based on catchup + git diff
  4. Then proceed with task

Important: Where Files Go

  • Templates are in ${CLAUDE_PLUGIN_ROOT}/templates/
  • Your planning files go in your project directory
Location What Goes There
Skill directory (${CLAUDE_PLUGIN_ROOT}/) Templates, scripts, reference docs
Your project directory task_plan.md, findings.md, progress.md

Quick Start

Before ANY complex task:

  1. Create task_plan.md — Use templates/task_plan.md as reference
  2. Create findings.md — Use templates/findings.md as reference
  3. Create progress.md — Use templates/progress.md as reference
  4. Re-read plan before decisions — Refreshes goals in attention window
  5. Update after each phase — Mark complete, log errors

Note: Planning files go in your project root, not the skill installation folder.

The Core Pattern

Context Window = RAM (volatile, limited)
Filesystem = Disk (persistent, unlimited)

→ Anything important gets written to disk.

File Purposes

File Purpose When to Update
task_plan.md Phases, progress, decisions After each phase
findings.md Research, discoveries After ANY discovery
progress.md Session log, test results Throughout session

Read the full file on GitHub · 186 lines

Files

What ships with it

9 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. 10d ago First seen · 186 lines · 56 tokens per session scan A 07bbe40e0edb

Subscribe to this mod's changes

planning-with-files is a skill published in the GitHub repository MuduiClaw/ClawKing (11 stars, last pushed 4mo ago), licensed MIT. It adds 56 tokens to every session and 1,447 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 78% identical to planning-with-files, differing in 69 lines, and is treated as a copy.

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