forge-status

A status command for a forge project, showing its plan, work modules, retry history, and saved learnings.

In plain words
What is it for?
It is for displaying the module dependency graph, attempt counts, statuses, scores, and recent project or global patterns.
Why use it?
It gives a current view of what is complete, pending, or failed without manually checking project files and iteration records.

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/tt-wang/forge/forge-status
Any agent
npx skills add TT-Wang/forge --skill forge-status
Clone the repo
git clone --depth 1 https://github.com/TT-Wang/forge

Made for: Claude Code, Codex.

Per session 14 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 281 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.00014 $0.00281
Opus 5 $0.00007 $0.00140
Sonnet 5 $0.00003 $0.00056
Haiku 4.5 $0.00001 $0.00028

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

Security

Grade A, and why

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

skills/forge-status/SKILL.md · 36 lines

What it actually says

Show the current status of the forge project. Prefix all output with [forge:status].

  1. Find the latest plan in .forge/plans/ (most recent JSON)
  2. Read it and display the module DAG
  3. For each module, call mcp__forge__iteration_state to get attempt history
  4. Check .forge/memory/project.jsonl for saved learnings
  5. Report:
## Forge Status

**Plan:** {objective}
**Created:** {timestamp}

### Modules
| ID | Title | Deps | Attempts | Status | Last Score |
|----|-------|------|----------|--------|------------|
| m1 | ...   | —    | 2        | passed | 1.0        |
| m2 | ...   | m1   | 0        | pending| —          |

### Memory
- {count} project patterns saved
- {count} global patterns saved

### Recent Learnings
- "{pattern}" (category, confidence)

If no plan exists, say "No active forge plan. Run /forge to start."

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 · 36 lines · 14 tokens per session scan A 8fa7a874e846

Subscribe to this mod's changes

forge-status is a skill published in the GitHub repository TT-Wang/forge (35 stars, last pushed 2mo ago), licensed MIT. It adds 14 tokens to every session and 281 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-30.