What is mission-status?

A read-only command that reports the current state of a software mission, including its goal, progress, verdicts, logs, and worktree.

Use it to inspect the latest mission or a named mission, see its current step and retry counts, and review recent log entries.

It gathers mission details from project files so you can check progress without opening each state and log file manually.

mission-status — Command by rajconnects

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 commands/rajconnects/founder-stack/mission-status

Clone the repo

git clone --depth 1 https://github.com/rajconnects/founder-stack

Or install founder-stack, the plugin that ships this one along with the rest of its 21 commands, 13 agents.

Per session 25 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 529 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.00025	$0.00529
Opus 5	$0.00013	$0.00264
Sonnet 5	$0.00005	$0.00106
Haiku 4.5	$0.00003	$0.00053

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

Security

Grade A, and why

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

workflow-v1/commands/mission-status.md · 49 lines

What it actually says

You are rendering a status summary for an in-flight or completed mission.

Arguments: $ARGUMENTS

Steps

Read .claude/project.json → mission_root (default missions/).
Resolve mission id:
- If $ARGUMENTS is non-empty: use it.
- Else: bash -c 'ls -1t <mission_root> 2>/dev/null | head -1' to find the latest mission directory. If empty: print No missions found in <mission_root>. and stop.
Read <mission_root>/<id>/state.json. If absent or invalid: print ERROR: state.json missing or invalid at <path>. and stop.
Read <mission_root>/<id>/log.md. Extract the last 20 lines (or fewer if shorter).

Render to the user:

Mission: <id>
Goal:    <goal>
Status:  <status>           (pace: <pace>)
Step:    feature <fid> | <current_step>
Caps:    <retry_counts[<fid>:worker]>/<caps.max_dispatches_per_feature> worker retries, <dispatches_total>/<caps.max_total_dispatches> total dispatches
Worktree: <state.worktree.path> (branch <state.worktree.branch>, base <state.worktree.base_ref>)
           — or "none (host mode)" if state.worktree is null/absent

Features:
  <fid> <name>  status=<status>  scrutiny=<verdict>  user_test=<verdict>
  ...

Recent log:
<last 20 lines of log.md>

If status == blocked: end with Next action: review <mission_root>/<id>/log.md and the latest handoff, then /mission-resume <id> (after fixing root cause) or /mission-abort <id>.
If status == completed: end with Mission complete. Suggested next: review <mission_root>/<id>/contract.md and consider gh pr create.

Notes

Read-only. Never modify state.json from this command.
If multiple missions are in flight, the user is expected to pass the id. The "latest" default is a convenience for single-mission workflows.

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.

2d ago First seen · 49 lines · 25 tokens per session scan A 9c770dd04ba3

Subscribe to this mod's changes

mission-status is a command published in the GitHub repository rajconnects/founder-stack (2 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 529 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.

Project management

mission-status

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

Steps

Notes

What this file has done since we first saw it

Other commands, from other repositories

git

checklist

clarify

specify

analyze

converge