What is status-check?

A read-only dashboard workflow showing the live state of a multi-worker coding project. It reports active workers, available and blocked tasks, unanswered questions, overlapping work, and lease health.

Use it when joining a project session to see what is running, what is stuck, which tasks are ready, and what work is already claimed.

It answers where work currently stands without changing the project or orchestrator state.

status-check — Skill for Claude Code and Codex by firatcand: A read-only dashboard workflow showing the live state of…

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/firatcand/forge/status-check

Any agent

npx skills add firatcand/forge --skill status-check

Clone the repo

git clone --depth 1 https://github.com/firatcand/forge

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/firatcand/forge/status-check.svg)](https://agentmods.dev/skills/firatcand/forge/status-check)

Your own site

<a href="https://agentmods.dev/skills/firatcand/forge/status-check"><img src="https://agentmods.dev/badge/skills/firatcand/forge/status-check.svg" alt="Measured on agentmods" height="20"></a>

Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 995 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.

Model	Per session	Once invoked
Fable 5	$0.00048	$0.00995
Opus 5	$0.00024	$0.00498
Sonnet 5	$0.00010	$0.00199
Haiku 4.5	$0.00005	$0.00100

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

Security

Grade A, and why

status-check 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 5d 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/status-check/SKILL.md · 46 lines

How it starts

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

/status-check

Distinct from /sync-status. /sync-status reconciles the tracker against plans/phases.yaml (is a phase ready to gate? any orphan issues?). /status-check shows live orchestrator runtime state — which workers are running right now, what's claimed, what's stuck. When in doubt: "what can I gate?" → /sync-status; "where am I right now?" → /status-check.

Read-only cockpit for driving one or many parallel orchestrator sessions. Answers the cold-start question: I just sat down — what's running, what's stuck, what can I pick up? Works standalone — no /forge orchestrate dispatch loop required.

Steps

Run the dashboard verb (one call, read-only).
```
forge orchestrate dashboard --json
```
In this dev repo (where the globally-installed forge binary may lag the source), use the dev entry instead:
```
node --import tsx src/bin/forge.ts orchestrate dashboard --json
```
The verb prints a { ok, data } envelope. data has: active_sessions, open_questions, ready_tasks, blocked_tasks, overlap_warnings, lease_health, source, and warnings. It never mutates state and degrades gracefully (empty ready_tasks/blocked_tasks + source.ready_blocked: "unavailable" when phases.yaml is missing).
Render a human summary grouped into four panels:
- Active workers — each active_sessions[] run with its claimed_tasks.
- Open questions — each open_questions[] as [<question_id>] <task_id> — <decision_key>.
- Ready vs blocked — ready_tasks (pickup candidates) and blocked_tasks (with their blocked_by).
- Warnings — overlap_warnings (file collisions between in-flight tasks) and any lease_health entry whose status is expiring_soon or stale. Surface any warnings[] entries verbatim.
Honor the source label. ready_tasks/blocked_tasks come from the LOCAL plans/phases.yaml cache (source.ready_blocked: "local-cache"). State this when you present them: "ready/blocked is from the local cache — run /reconcile for tracker truth." This is also a best-effort, non-atomic snapshot: files can change mid-read, so a momentary mismatch (e.g. a task shown running with an already-released lease) is expected, not a bug.

Read the full file on GitHub · 46 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.

5d ago First seen · 46 lines · 48 tokens per session scan A 87d06a9f3b5e

Subscribe to this mod's changes

status-check is a skill published in the GitHub repository firatcand/forge (13 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session and 995 once invoked, about $0.0002 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.

Building agents Project management agentic-coding ai-coding-agent claude-code codex compound-engineering spec-driven-development

ospec-change

Create or advance a lightweight OSpec change using the classic fast workflow.

clawplays/ospec · 18 tokens

prospec-knowledge-generate

Generate AI Knowledge - Read raw-scan.md, analyze project structure, autonomously decide module boundaries, and produce Recipe-First module READMEs and index. Triggers: generate knowledge, analyze project, module split, 產生知識, 知識庫, 分析專案, 模組拆分.

benwu95/prospec · 71 tokens

submit-pr

Open a prospec pull request in the house format — push the change's two commits, write the Traditional Chinese body, and link it to its issue. Triggers: submit pr, open pr, 開 PR, 送 PR, 發 PR, pull request, 提交 PR.

benwu95/prospec · 59 tokens

prospec-explore

Explore - Requirement exploration, problem investigation, and solution comparison partner. Triggers: explore, compare, investigate, unsure, clarify, 探索, 比較, 釐清, 調查, 不確定.

benwu95/prospec · 50 tokens

prospec-plan

Plan Implementation - Convert User Story into technical implementation plan (plan.md) and change specification (delta-spec.md). Triggers: plan, architecture, technical plan, 規劃, 架構規劃, 技術規劃.

benwu95/prospec · 53 tokens

prospec-knowledge-update

Incremental Knowledge Update - Parse delta-spec.md to identify affected modules, scan source code, and update module README, index.md, and module-map.yaml incrementally. Triggers: knowledge update, incremental update, sync knowledge, update docs, 更新知識, 增量更新, 同步知識, 更新文件.

benwu95/prospec · 70 tokens