track

A progress report for one zforge feature, based on its planning documents. It shows completed phases, checklist and evidence gaps, standing warnings, recent activity, and open decisions.

In plain words
What is it for?
Use it to check the current state of a zforge feature by name and identify the next unresolved planning or verification work.
Why use it?
It lets you see what a planned feature still owes and whether reported work has supporting evidence.

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/langerrr/zforge/track
Any agent
npx skills add Langerrr/zforge --skill track
Clone the repo
git clone --depth 1 https://github.com/Langerrr/zforge

Made for: Claude Code, Codex.

Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 630 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.00021 $0.00630
Opus 5 $0.00010 $0.00315
Sonnet 5 $0.00004 $0.00126
Haiku 4.5 $0.00002 $0.00063

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

Security

Grade A, and why

track 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.

codex/skills/track/SKILL.md · 57 lines

How it starts

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

Feature Progress

Show where a feature stands, including what it owes.

Arguments

  • $1: Feature name (snake_case or will be converted)

Process

  1. Convert the feature name to snake_case and locate docs/{feature_name}/05_progress_overview.md, falling back to {feature_name}/05_progress_overview.md.
  2. If not found: "No plan found for '{feature_name}'. Run $zforge:plan {name} to create one."
  3. Read the overview, every phase file, and decision_review.md.

Phase status comes from each phase file's > Status: header. There are no signals to scan for.

Report

## {Feature Name} — Progress

Phases: {completed}/{total}

Phase  Name                 Status      Checklist  Evidence      Last Activity
──────────────────────────────────────────────────────────────────────────────
1      Backend Schema       COMPLETED   5/5        E2 / E2       2026-02-08
2      Backend API          REPORTED    7/7        E2 / E2 *     2026-02-09
3      Frontend Types       PENDING     0/4        — / E1        —
4      Frontend Pages       PENDING     0/6        — / E4        —
5      Console Vocabulary   PENDING     0/3        — / J2        —

* claimed, not re-run — Phase 2 is REPORTED

### Standing Flags (2 open)
- SF1 (Phase 5): E4 unmet across all UI phases — closes when a browser-executed run passes
- SF3 (Phase 7): live vendor calls deferred to a mock adapter — closes when a token exists

### Decisions awaiting review: 14 🟡
- Most recent: P7.1 — tri-state run status supersedes P2.8

### Open Items
- Phase 2 · question · migration ordering under concurrent writes — unresolved

The Evidence column reads achieved / required, and classes compare within their axis — an E row and a J row are not ranked against each other. A phase showing — / E4 has not yet demonstrated the class its plan asked for.

A completed phase showing anything below its requirement resolved that gap one of two ways: a standing flag against it, or reasoning in its ## Acceptance for why the shortfall was immaterial. Either is an answer. A shortfall with neither is the finding — say so, and name the row.

Read the full file on GitHub · 57 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. 2d ago First seen · 57 lines · 21 tokens per session scan A 2bcf1d34748e

Subscribe to this mod's changes

track 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 630 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.

Related

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…

Junhanliu-dev/espalier-engineering · 1,095 tokens

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…

Junhanliu-dev/espalier-engineering · 118 tokens

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…

JustMichael-80/MasterVault · 104 tokens

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…

juanklagos/spec-driven-development-template · 80 tokens

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…

juanklagos/spec-driven-development-template · 84 tokens

eo-brainstorming

对不成形的想法做发散、对抗、拆解和方向决策。触发:帮我想想 / 头脑风暴 / brainstorming / /eo-brainstorming。 NOT FOR: 普通技术讨论或具体实现问题(只在用户明确"想想方向"时触发)。.

SimpleEve/eo-skills · 75 tokens