agentmods.dev

planning-with-files

planning-with-files is a skill for Claude Code from LuizEduPP/Rememb. It costs 50 tokens per session (1,861 once invoked), scanned A, a copy of planning-with-files, MIT.

A file-based planning method for complex, multi-step work. It stores plans, discoveries, and progress in Markdown files so the work can continue across long sessions.

In plain words
What is it for?
It is for breaking projects or research into tasks, recording findings, restoring context, and tracking progress across tool calls or sessions.
Why use it?
It reduces the risk of losing decisions, research findings, or unfinished steps when the conversation becomes long or the session stops.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter. Also seen: names the TodoWrite tool.

not rated 5repo 17d ago A scan 50 tokens copy · 78% MIT

Good fit It is for breaking projects or research into tasks, recording findings, restoring context, and tracking progress across tool calls or sessions.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/luizedupp/rememb/planning-with-files
View source ↗ LuizEduPP/Rememb
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 LuizEduPP/Rememb --skill planning-with-files
Clone the repo
git clone --depth 1 https://github.com/LuizEduPP/Rememb

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/luizedupp/rememb/planning-with-files/github.svg)](https://agentmods.dev/skills/luizedupp/rememb/planning-with-files)
Your own site
<a href="https://agentmods.dev/skills/luizedupp/rememb/planning-with-files"><img src="https://agentmods.dev/badge/skills/luizedupp/rememb/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/luizedupp/rememb/planning-with-files"><img src="https://agentmods.dev/badge/skills/luizedupp/rememb/planning-with-files.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,861 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.00050 $0.01861
Opus 5.5 $0.00020 $0.00744
Sonnet 5.5 $0.00010 $0.00372
Haiku 4.5 $0.00005 $0.00186

Measured 1mo ago against content hash 34b5d25aa646, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 1mo ago.

The scan reads SKILL.md. This mod also ships 5 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 — 111 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.

src/rememb_skills/planning-with-files/SKILL.md · 244 lines

How it starts

The opening of the file, as written. The whole thing — 244 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."

Overview

Use persistent project files to store task state, discoveries, and progress so long-running work survives context limits and session resets.

Optional Host Integration

Some AI hosts support hooks, tool restrictions, or lifecycle automation. Treat those as optional enhancements, not required behavior. The core workflow in this document should still work in any IDE, editor, CLI, or chat app.

First: Restore Context

Before doing anything else, check if planning files exist and read them:

  1. If task_plan.md exists, read task_plan.md, progress.md, and findings.md immediately.
  2. Then check for unsynced context from a previous session:
# Linux/macOS
$(command -v python3 || command -v python) <skill-root>/scripts/session-catchup.py "$(pwd)"

# Windows PowerShell
& (Get-Command python -ErrorAction SilentlyContinue).Source "<skill-root>/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

Where Files Go

  • Templates are in <skill-root>/templates/
  • Your planning files go in your project directory
Location What Goes There
Skill directory (<skill-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

Read the full file on GitHub · 244 lines

Files

What ships with it

10 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. 1mo ago First seen · 244 lines · 50 tokens per session scan A 34b5d25aa646

Subscribe to this mod's changes

planning-with-files is a skill published in the GitHub repository LuizEduPP/Rememb (5 stars, last pushed 17d ago), licensed MIT. It adds 50 tokens to every session and 1,861 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 78% identical to planning-with-files, differing in 111 lines, and is treated as a copy.

LLMPlanningProject managementagent-memoryai-agentsclaudecontext-persistencecursor
Related

Other skills, from other repositories

tasks

Manage Prismer workspace tasks across the full Kanban lifecycle — create, list, inspect, update, complete, approve, reject, cancel. Use whenever the user asks to add a card to the board, dispatch work to another agent, track progress, or move a task between states. Executes via the cloud task CLI.

Prismer-AI/PrismerCloud · 68 tokens

prismer-notion

Notion API + ntn CLI: pages, databases, markdown, Workers.

Prismer-AI/PrismerCloud · 21 tokens

test-result-feedback

Close the acceptance loop for a tested change — consume the apc test TierResult, map EACH acceptance criterion to a pass/fail outcome from structured fields (never chat text), attach an evidence ref, and write it back to the task. A SUT red is a finding, never softened to green.

Prismer-AI/PrismerCloud · 65 tokens

doc-sync

Before merge, mechanize Documentation-First — derive the code delta from git diff, then verify required docs are in sync (CHANGELOG, docs/api, CLAUDE.md/ROADMAP). Any SDK-package change must carry a matching CHANGELOG entry + aligned version files. A change that skipped a required doc is flagged as a gap; a…

Prismer-AI/PrismerCloud · 79 tokens

spec-intake

Turn one atomic feature/gap request into a dispatchable task in a single pass — create the task, write SPEC.md (auto-folded into linkedAssetIds server-side), add acceptance criteria, record provenance. Two-part epics are refused, not silently split.

Prismer-AI/PrismerCloud · 57 tokens

prismer-teams-meeting-pipeline

Teams meeting summaries, job replay, Graph subscriptions.

Prismer-AI/PrismerCloud · 19 tokens