status

A command that displays a dashboard for a task-based coding workflow. It reports phases, task counts, health checks, verification results, costs, active work, and failures.

In plain words
What is it for?
Use it to monitor task completion, inspect failed or blocked work, review verification health, or retrieve status as JSON.
Why use it?
It brings the workflow's progress and problems into one status view instead of requiring separate checks.

Command

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/dowwie/tasker/status
Clone the repo
git clone --depth 1 https://github.com/Dowwie/tasker
Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 143 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.00010 $0.00143
Opus 5 $0.00005 $0.00072
Sonnet 5 $0.00002 $0.00029
Haiku 4.5 $0.00001 $0.00014

Measured yesterday against content hash 14fb00ffacde, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

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.

internal/commands/status.md · 30 lines

What it actually says

Run the status command to display a workflow dashboard:

tasker state status --once

This shows:

  • Current phase and target directory
  • Progress (completed/total tasks, current phase)
  • Status breakdown (completed, running, failed, blocked, pending)
  • Health checks (DAG validation, steel thread, verification commands)
  • Verifier calibration score
  • Cost metrics (tokens, USD)
  • Active tasks currently running
  • Recent failures

For interactive TUI mode, use:

tasker tui

For JSON output:

tasker state status --json
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. yesterday First seen · 30 lines · 10 tokens per session scan A 14fb00ffacde

Subscribe to this mod's changes

status is a command published in the GitHub repository Dowwie/tasker (19 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 10 tokens to every session and 143 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.