task-status

A command that shows the current state of one PitWay task, including its dependencies and recorded result. It can also produce the small set of files and instructions needed by a worker assigned to that task.

In plain words
What is it for?
Use it to inspect a task during development or create its minimal execution context before dispatching work.
Why use it?
It lets you check task progress without loading the entire workflow, while keeping dispatched workers focused on the information they need.

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/thixpin/pitway/task-status
Clone the repo
git clone --depth 1 https://github.com/thixpin/pitway
Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 257 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.00257
Opus 5 $0.00007 $0.00129
Sonnet 5 $0.00003 $0.00051
Haiku 4.5 $0.00001 $0.00026

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

Security

Grade A, and why

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

src/integrations/claude/commands/task-status.md · 28 lines

What it actually says

task-status

Role: either (read-only)

pitway task-status <id> [--context] [--json]

Two distinct uses, gated by --context:

  • Without it: a quick look at one task's status, its dependencies, and its recorded result — useful mid-conversation without pulling the full dispatch bundle. With --json it also carries the task's declared scope (relevantFiles, or contextFiles + writeScope, whichever the task declares) and its verification (strategy, detail, timeoutMs when declared) — the fields a task-amend file must restate (M045).
  • With --context --json: produces the minimal task-context bundle that goes to a dispatched worker — the one and only source of that bundle. See ../dispatch.md for where this fits in the dispatch sequence and exactly what "minimal" means here.

See ../protocol-driver.md. Run pitway task-status --help for flags.

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 · 28 lines · 0 tokens per session scan A 994d0c31d26b

Subscribe to this mod's changes

task-status is a command published in the GitHub repository thixpin/pitway (19 stars, last pushed 3d ago), licensed MIT. It adds 14 tokens to every session and 257 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.