aster-planning

aster-planning is a skill for Claude Code, Codex from Zfinix/aster. It costs 72 tokens per session (1,061 once invoked), scanned A, original, Apache-2.0.

A planning guide for breaking complex coding tasks into ordered steps and tracking their progress. It stores plans in the project so they can be reviewed and updated.

In plain words
What is it for?
Use it to plan work across several files or parts of a system, prepare a roadmap, or regroup after a failed attempt. It is also useful when you want approval before implementation.
Why use it?
It prevents large, dependent tasks from becoming an unclear sequence of edits. It also makes the current status and unfinished work visible.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to plan work across several files or parts of a system, prepare a roadmap, or regroup after a failed attempt. It is also useful when you want approval before implementation.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/zfinix/aster/aster-planning
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 Zfinix/aster --skill aster-planning
Clone the repo
git clone --depth 1 https://github.com/Zfinix/aster

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 aster-planning

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/zfinix/aster/aster-planning"><img src="https://agentmods.dev/badge/skills/zfinix/aster/aster-planning.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 72 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,061 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.00072 $0.01061
Opus 5.5 $0.00029 $0.00424
Sonnet 5.5 $0.00014 $0.00212
Haiku 4.5 $0.00007 $0.00106

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

Security

Grade A, and why

aster-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 1mo 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/aster-planning/SKILL.md · 116 lines

How it starts

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

Planning and executing multi-step tasks

When a task is too large for a single turn, break it into a plan, get approval, then execute step by step, marking progress as you go.

When to plan

Plan when any of these are true:

  • The task spans three or more files.
  • The user asks for a plan, roadmap, or breakdown.
  • The user says "how would you approach" or similar.
  • The task has dependencies between steps.
  • You are unsure of the approach and want confirmation before acting.
  • A prior attempt failed and you need to regroup.

Do not plan for single-file, single-step changes. Just do them.

The plan file

Plans live at .aster/plans/<slug>.md. The slug is a short kebab-case description: add-rate-limiting, split-app-component. If .aster/plans/ does not exist, create it with edit_file (the directory is created automatically).

Format

---
status: draft
created: <ISO 8601>
updated: <ISO 8601>
---

# Plan: <one-line goal>

## 1. <phase name>
- [ ] <concrete, verifiable task>
- [ ] <another task>

## 2. <next phase>
- [ ] <task>

Rules

  • status: draft (not yet approved), active (approved, executing), done (all tasks complete), abandoned (no longer pursuing).
  • Phases are ordered groups of related tasks. Most plans have 2–5 phases.
  • Tasks are concrete and verifiable. "Refactor the auth module" is vague; "Extract validate_token from auth.rs into auth/validation.rs" is concrete. Every task should produce a visible change: a file exists, a test passes, a function is extracted.
  • Checkboxes: [ ] pending, [~] in progress, [x] done, [!] blocked. Only one task in progress at a time.

The planning loop

1. Create

Write the plan file with status: draft. Include enough detail that the user can judge the approach without reading your mind. Keep it at the level of "what changes and in what order," not "which key I'll press."

2. Present

Show the plan to the user in a few lines: the goal, the phases, and one sentence on the approach. Ask whether to proceed. Do not begin executing until they confirm.

Read the full file on GitHub · 116 lines

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 · 116 lines · 72 tokens per session scan A 675725aa1c9c

Subscribe to this mod's changes

aster-planning is a skill published in the GitHub repository Zfinix/aster (132 stars, last pushed yesterday), licensed Apache-2.0. It adds 72 tokens to every session and 1,061 once invoked, about $0.0003 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.