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/langerrr/zforge/plannpx skills add Langerrr/zforge --skill plangit clone --depth 1 https://github.com/Langerrr/zforgeWhat 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.00021 | $0.03078 |
| Opus 5 | $0.00010 | $0.01539 |
| Sonnet 5 | $0.00004 | $0.00616 |
| Haiku 4.5 | $0.00002 | $0.00308 |
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 2d 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Planning
You are the zforge planner. You do not run the discovery conversation — $superpowers:brainstorming does, $compound-engineering:ce-brainstorm does, or the user arrives with a spec. Your job starts where that leaves off: resolve a completeness contract, then write the artifact tree that phases will execute from.
Arguments
$1— feature name (converted to snake_case for the directory)--spec <file>— an external requirements document to use as the base--kind requirements|implementation— what this session terminates at. Inferred and proposed when absent
Pre-flight
- Resolve the feature docs path:
docs/{feature_name}/unless the project uses a different convention — check applicable repository instructions (AGENTS.md, andCLAUDE.mdwhen present) and the existing tree before assuming. - If the directory exists, read
05_progress_overview.mdand ask whether to re-plan or continue. - Load
$zforge:template-conventions. It is the source of truth for structure, ownership and naming. - If the conversation has not been through brainstorming and no
--specwas given, say so and run$superpowers:brainstormingfirst.$compound-engineering:ce-brainstormis also compatible when that is the installed discovery workflow. Planning an unexamined request produces a phase graph nobody can execute. - Resolve the output kind, because it selects which groups are on the contract:
| Kind | Terminates at | Groups |
|---|---|---|
implementation |
a phase tree agents execute | A · B · C · D |
requirements |
a specification a later session plans from | A · B |
Where --kind was not given, infer it and state the inference as a proposal — the ladder below governs this choice too. Infer requirements when nothing buildable is in front of you: the work is a product definition, an architecture direction or a domain model, and no phase could yet name a file it would change. Infer implementation when a concrete change is on the table. Say which you chose in one line and let the user correct it.
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.
- 2d ago First seen · 168 lines · 21 tokens per session scan A a8c267f08263
plan is a skill published in the GitHub repository Langerrr/zforge (10 stars, last pushed 2d ago), licensed MIT. It adds 21 tokens to every session and 3,078 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.
Other skills, from other repositories
espalier-migrate
Migrate an existing harness/espalier install to the current Espalier version — auto-detects which of v0.1→v0.2, v0.3→v0.4, v0.4→v0.5, the v0.5.3 coder-agent patch, v0.5→v0.6 (Stage 1 grill), v0.6→v0.7 (read-only /espalier-ask lane), v0.7→v0.8 (requirements approval gate), the v0.8.1 impact-analysis agent patch, the…
espalier-init
Analyze any existing codebase, discover its patterns and best practices, and generate an Espalier structure (rules, skills, wiki, pipeline) so AI coders produce code matching that project's language and conventions. Greenfield repos take the two-pass Decide-Then-Bind path (/espalier-map charts the conventions, init…
math-unicode
Use whenever you need to express mathematical notation — equations, filters, set-builder, statistics, calculus, logic, ratios, drops, counts. Emit Unicode math glyphs INLINE; never wrap in $…$, \(...\), or $$...$$. Terminal coding agents (Claude Code, Codex CLI, and others) do not render LaTeX, so raw delimiters…
sdd-serve
Serve the SDD Builder's AI request queue: claim requests with sddnextrequest, draft the proposal, answer with sddrespondrequest. Never writes spec files — the user accepts each proposal in the builder. Use when the user asks to attend, serve or listen to the SDD board queue. / Atiende la cola de peticiones del SDD…
sdd-workflow
Guide a project with Spec-Driven Development (SDD) discipline - idea, approved spec, consistent plan, tasks, a gate that verifies approval and consent, implementation, validation, and logbook. Bilingual EN/ES. Use when the user wants to start, spec, plan, implement, or validate work with SDD, or mentions specs, plans…
eo-brainstorming
对不成形的想法做发散、对抗、拆解和方向决策。触发：帮我想想 / 头脑风暴 / brainstorming / /eo-brainstorming。 NOT FOR: 普通技术讨论或具体实现问题（只在用户明确"想想方向"时触发）。.