plan

plan is a skill for Claude Code, Codex from Supersynergy/awesome-agentic-coding. It costs 19 tokens per session (291 once invoked), scanned A, original, MIT.

A procedure for planning a complex coding task before writing code. It calls for researching the existing project, outlining the approach, and checking the plan before implementation.

In plain words
What is it for?
Use it to investigate relevant files and tests, define steps and edge cases, state what is out of scope, and present a plan for review.
Why use it?
It reduces misunderstandings, missed test patterns, and unnecessary work by agreeing on the intended changes first.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/supersynergy/awesome-agentic-coding/plan
Any agent
npx skills add Supersynergy/awesome-agentic-coding --skill plan
Clone the repo
git clone --depth 1 https://github.com/Supersynergy/awesome-agentic-coding

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 plan

README.md
[![agentmods](https://agentmods.dev/badge/skills/supersynergy/awesome-agentic-coding/plan.svg)](https://agentmods.dev/skills/supersynergy/awesome-agentic-coding/plan)
Your own site
<a href="https://agentmods.dev/skills/supersynergy/awesome-agentic-coding/plan"><img src="https://agentmods.dev/badge/skills/supersynergy/awesome-agentic-coding/plan.svg" alt="Measured on agentmods" height="20"></a>
Per session 19 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 291 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00019 $0.00291
Opus 5 $0.00010 $0.00146
Sonnet 5 $0.00004 $0.00058
Haiku 4.5 $0.00002 $0.00029

Measured 3d ago against content hash c5a2be6597a3, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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 3d 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.

skills/plan/SKILL.md · 49 lines

What it actually says

Planning Protocol

Task: $ARGUMENTS

Phase 1: Research (Parallel Haiku Agents)

Launch 2-3 parallel researcher agents to:

  • Find existing code relevant to this task
  • Find test patterns used in this project
  • Find similar implementations in the codebase

Phase 2: Plan

Based on research, create a structured plan:

## Goal
[1 sentence: what does "done" look like?]

## Approach
[Which files to create/modify and why]

## Steps
1. [First change — most foundational]
2. [Second change — builds on first]
3. [Tests — verify behavior]

## Edge Cases
- [What could go wrong?]
- [What inputs are unexpected?]

## Not Doing
- [What's explicitly out of scope?]

Phase 3: Review

Present the plan and wait for user feedback before proceeding.

Rules

  • NEVER write code during planning — plan ONLY
  • Keep plans under 50 lines — if longer, the task should be split
  • Include "Not Doing" to prevent scope creep
  • Surface assumptions early — better to ask than guess wrong
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. 3d ago First seen · 49 lines · 19 tokens per session scan A c5a2be6597a3

Subscribe to this mod's changes

plan is a skill published in the GitHub repository Supersynergy/awesome-agentic-coding (1 stars, last pushed 1mo ago), licensed MIT. It adds 19 tokens to every session and 291 once invoked, about $0.0001 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.