A project status view summarises an epic's running, available, blocked, and completed tasks. It also maps which files active tasks own and identifies work that could be done in parallel.

Use it to inspect task dependencies, active work, file ownership, unclaimed files, parallel opportunities, and the project's worktree and execution settings.

It shows not only how much work is done, but why other work may be waiting and where people or agents might conflict. This makes the next safe task easier to choose.

status — Command by skullninja

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/skullninja/coco-workflow/status

Clone the repo

git clone --depth 1 https://github.com/skullninja/coco-workflow

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

When invoked 649 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.00017	$0.00649
Opus 5	$0.00009	$0.00324
Sonnet 5	$0.00003	$0.00130
Haiku 4.5	$0.00002	$0.00065

Measured 2d ago against content hash a7a0806b6fde, 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 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.

commands/status.md · 113 lines

How it starts

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

User Input

$ARGUMENTS

Setup

If $ARGUMENTS contains an epic ID, use it. Otherwise, find the most recent open epic:
```
coco-tracker epic-status
```
Pick the most recent non-closed epic from the output.

Execution

1. Get Epic State

coco-tracker epic-status {epic-id}

coco-tracker list --json --epic {epic-id}

2. Categorize Tasks

Group tasks by status:

Running (in_progress): Currently being worked on
Available (pending, not blocked): Ready to start
Blocked (pending, has unresolved blockers): Waiting on dependencies
Completed: Done

3. File Ownership Map

For each running task, read owns_files from metadata (if present) and display:

File Ownership
==============
Task {id} ({title}):
  - {file pattern 1}
  - {file pattern 2}

Unclaimed:
  - {remaining file patterns}

4. Parallel Opportunities

Identify tasks that could run in parallel right now:

Parallel Opportunities
======================
Available tasks with no file conflicts:
  1. {task title} (no overlap with running tasks)

Cannot parallelize:
  - {task title} (blocked by {blocking-tasks})

5. Worktree / Parallel Status

Read loop.parallel.enabled from .coco/config.yaml. If parallel execution is enabled:

Parallel Execution
==================
Mode: {enabled | disabled}
Max agents: {max_agents}

Active Worktrees:
  - worktree-{task-id}: {task title} ({status: running | completed | failed})
    Branch: {issue-branch}
    PR: #{pr-number} ({review status})

Merge Queue:
  - PR #{N}: {task title} (awaiting review)

Recently Completed:
  - {task-id}: {title} -- merged via PR #{N}

If parallel execution is not enabled, skip this section.

6. Dependency Graph

Show the dependency tree with status indicators:

Dependency Graph
================
[x] Phase 1: Setup
[x] Phase 2: Foundational
  +-- [>] Phase 3: US1 (in_progress)
  +-- [ ] Phase 4: US2 (available)
  +-- [~] Phase 5: Polish (blocked by 3, 4)

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

2d ago First seen · 113 lines · 17 tokens per session scan A a7a0806b6fde

Subscribe to this mod's changes

status is a command published in the GitHub repository skullninja/coco-workflow (7 stars, last pushed 2d ago), licensed MIT. It adds 17 tokens to every session and 649 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 ai-coding ai-workflow anthropic autonomous-coding claude-code claude-code-plugin

status