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.
npx agentmods add skills/zfinix/aster/aster-planningnpx skills add Zfinix/aster --skill aster-planninggit clone --depth 1 https://github.com/Zfinix/asterWrote 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.
[](https://agentmods.dev/skills/zfinix/aster/aster-planning)<a href="https://agentmods.dev/skills/zfinix/aster/aster-planning"><img src="https://agentmods.dev/badge/skills/zfinix/aster/aster-planning.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00072 | $0.01061 |
| Opus 5 | $0.00036 | $0.00531 |
| Sonnet 5 | $0.00014 | $0.00212 |
| Haiku 4.5 | $0.00007 | $0.00106 |
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 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.
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_tokenfromauth.rsintoauth/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.
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.
- 3d ago First seen · 116 lines · 72 tokens per session scan A 675725aa1c9c
aster-planning is a skill published in the GitHub repository Zfinix/aster (40 stars, last pushed 8d ago), licensed Apache-2.0. It adds 72 tokens to every session and 1,061 once invoked, about $0.0004 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-30.
Other skills, from other repositories
new-plugin
Factory line for adding a new HAR verification plugin (like playwright or rocketsim) for any framework — research the framework docs, build the template under src/templates/plugins/, register it everywhere, validate on a real repository, and open a PR. Use when asked to add/create a plugin, plugin template, or…
factory-line
Factory line for executing one station of a declared multi-station program — read the installed line bundle (har line status), plan parallel work into isolated HAR slots, run the cumulative gate with har line gate, and hand off for human review. Use when asked to "run a factory line", "run the next station", "execute…
v1-milestone
Factory line for executing one milestone of the HAR v1.0.0 refactor (epic os-factory/har#225) — plan the wave of parallel subagents, implement each issue in its own HAR slot, ship stacked PRs, run the fixture-e2e milestone gate, and hand off for review. Use when asked to "run the next v1 milestone", "work on v1.0.0"…
lemma-user
Operate an existing Lemma pod from the CLI as a human or agent: inspect resources, query tables and records under RLS, search and read pod files (converted markdown, page images), run functions and workflows, submit waiting workflow forms, chat with pod agents, run first-party tools, and execute third-party connector…
lemma-builder
Design and build complete Lemma pods: model tables/files/functions/agents/workflows/schedules/connectors/surfaces/apps from a problem statement, author a local pod bundle, import progressively with the Lemma CLI, and verify every layer. Use for pod design, creation, restructuring, import/export, and app development.…
lemma-evals
Design, run, and review repeatable evaluations for Lemma agents, functions, and workflows. Use when defining evaluation contracts and case datasets, comparing a baseline with a candidate revision or runtime, checking deterministic correctness or rubric-scored judgment, measuring repeated-run variance, testing…