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-clinpx skills add Zfinix/aster --skill aster-cligit clone --depth 1 https://github.com/Zfinix/asterWhat 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.00085 | $0.01133 |
| Opus 5 | $0.00043 | $0.00566 |
| Sonnet 5 | $0.00017 | $0.00227 |
| Haiku 4.5 | $0.00009 | $0.00113 |
Grade A, and why
aster-cli 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 yesterday.
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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Aster CLI
Aster is an AI coding agent that works in your repository: it reads and searches the code, answers questions, applies edits, and runs a review pipeline that forms hypotheses about defects, verifies them against the codebase, and reports shaped findings. It runs locally against the current repo and needs an aster.yaml (created by aster init).
Setup
aster init # pick a provider, write aster.yaml, store the API key
aster login # optional: link GitHub via device flow (needed for PR reviews)
aster init is interactive. Run it once per repo; keys are stored outside the repo so aster.yaml is safe to commit.
Reviewing code
aster review # review the current branch against its base
aster review main..HEAD # review an explicit range
aster review path/to/file.rs # review a single file
aster review --pr 123 # review a GitHub PR (requires aster login)
Review output is a list of findings. Prefer reviewing the smallest meaningful diff: a branch or range, not the whole repo.
Chat and fixes
aster chat # interactive TUI with the review agent
aster chat --print "question" # one-shot answer to stdout (use this from scripts and agents)
aster fix # apply model-generated fixes for findings (dry-run by default)
As an agent, always use aster chat --print rather than the TUI. aster fix never writes without an explicit apply flag; run it plain first and inspect the dry-run output.
Sessions and memory
aster sessions # list saved chat sessions for this repo
aster sessions show <id> # print a session's full transcript
aster memory # list stored durable memory
aster memory add "fact" # append a fact to project memory
aster memory add --title t "…" # save a titled memory block
Both accept --json; see below.
Skills
Aster loads agent skills from .aster/skills (project) and <config>/aster/skills (user-global).
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.
- yesterday First seen · 106 lines · 0 tokens per session scan A 54a1a54c4cf3
aster-cli is a skill published in the GitHub repository Zfinix/aster (40 stars, last pushed 6d ago), licensed Apache-2.0. It adds 85 tokens to every session and 1,133 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-research
Run rigorous, source-backed research in an existing Lemma pod. Use for investigations, literature or market scans, policy and product research, fact-checking, comparisons, current-information questions, and updates to prior research that require pod files, workspace material, or web sources; exact citations; explicit…