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/plan-statusnpx skills add Langerrr/zforge --skill plan-statusgit 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.00023 | $0.00358 |
| Opus 5 | $0.00012 | $0.00179 |
| Sonnet 5 | $0.00005 | $0.00072 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
plan-status 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.
What it actually says
Workspace Feature Status
Scan for all feature plans under the current working directory and display their status.
Process
-
Search for all
05_progress_overview.mdfiles under the current working directory using Glob:**/docs/*/05_progress_overview.md -
For each found file:
- Extract the feature name from the directory path
- Read the file and parse the phase summary table and the Standing Flags section
- Count: total phases, completed, running, pending, and open standing flags
-
Display a summary table:
Feature Plans in {current_directory}:
Feature Status Progress Flags Path
────────────────────────────────────────────────────────────────
ai_assistant In Progress 3/5 phases — docs/ai_assistant/
video_pipeline In Progress 1/3 phases 1 open docs/video_pipeline/
api_refactor Complete 2/2 phases — docs/api_refactor/
A feature with every phase complete and an open standing flag is not Complete. Show it as Flagged with the flag count — the whole point of tracking flags is that they survive the run ending.
-
List open standing flags below the table, with the phase that opened each and what closes it.
-
If no
05_progress_overview.mdfiles are found, report: "No feature plans found under {current_directory}."
Scope
ONLY look under the current working directory. Do not search parent directories or sibling projects.
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 · 40 lines · 23 tokens per session scan A c31133040f31
plan-status is a skill published in the GitHub repository Langerrr/zforge (10 stars, last pushed 2d ago), licensed MIT. It adds 23 tokens to every session and 358 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
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-flow
单点 handoff:把 eo- 任务(review/test/implement/change-review/spec-review)甩给 tmux 里的 codex pane 执行,回包后决定"甩回去修"或"暂停问用户"。触发:eo-flow / 甩给 codex / /eo-flow。 NOT FOR: 完整流水线(用 /eo-workflow)。.
eo-project-init
所有 eo- skill 的总入口。其它 skill(eo-change / eo-implement / eo-doc-manager / …)都依赖 .eo-project.json;未运行过本 skill 的项目无法使用其它 eo- skill。.
eo-workflow
在 tmux 多窗格中编排 eo- 技能流水线(module-init / change / implement / archive),跨 pane 自动派发和状态轮询。触发:eo-workflow / 启动工作流 / 全流程 / /eo-workflow。.
eo-project-update
更新项目进度、阶段状态、决策记录,并同步项目看板(若配置)。通过 .eo-project.json 定位项目。触发:更新项目 / 同步进展 / 记录决策 / 阶段完成 / /eo-project-update。.
eo-backlog
往项目 backlog.md 追加待办、灵感或未接入的未来规划。通过 .eo-project.json 定位项目。触发:加入 backlog / 记一条待办 / 以后再说 / /eo-backlog。.