status

status is a command for coding agents from wshobson/agents. It costs 10 tokens per session (1,869 once invoked), scanned A, original, MIT.

A command that summarizes a Conductor project's tracks, tasks, progress, and next actions.

In plain words
What is it for?
Use it to review overall project progress, find the current phase, and identify the next pending task.
Why use it?
It removes the need to manually inspect project plans to understand what is finished, active, or waiting.

Command

Part of the conductor plugin — 3 skills, 6 commands, 1 agent shipped together

About the project

Agentic Plugin Marketplace is a collection of reusable plugins, agents, skills, commands, and rules for coding-agent tools including Claude Code, Codex CLI, Cursor, OpenCode, Antigravity CLI, and GitHub Copilot. It is for developers assembling agentic workflows across multiple harnesses from shared Markdown sources, and the catalogue entries are examples or subsets of those workflow components.

wshobson/agents · 39,428 stars · on GitHub

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/wshobson/agents/status
Clone the repo
git clone --depth 1 https://github.com/wshobson/agents

Or install conductor, the plugin that ships this one along with the rest of its 3 skills, 6 commands, 1 agent.

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.

agentmods badge for status

README.md
[![agentmods](https://agentmods.dev/badge/commands/wshobson/agents/status.svg)](https://agentmods.dev/commands/wshobson/agents/status)
Your own site
<a href="https://agentmods.dev/commands/wshobson/agents/status"><img src="https://agentmods.dev/badge/commands/wshobson/agents/status.svg" alt="Measured on agentmods" height="20"></a>
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 1,869 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.01869
Opus 5 $0.00005 $0.00934
Sonnet 5 $0.00002 $0.00374
Haiku 4.5 $0.00001 $0.00187

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

plugins/conductor/commands/status.md · 320 lines

How it starts

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

Conductor Status

Display the current status of the Conductor project, including overall progress, active tracks, and next actions.

Pre-flight Checks

  1. Verify Conductor is initialized:

    • Check conductor/product.md exists
    • Check conductor/tracks.md exists
    • If missing: Display error and suggest running /conductor:setup first
  2. Check for any tracks:

    • Read conductor/tracks.md
    • If no tracks registered: Display setup complete message with suggestion to create first track

Data Collection

1. Project Information

Read conductor/product.md and extract:

  • Project name
  • Project description

2. Tracks Overview

Read conductor/tracks.md and parse:

  • Total tracks count
  • Completed tracks (marked [x])
  • In-progress tracks (marked [~])
  • Pending tracks (marked [ ])

3. Detailed Track Analysis

For each track in conductor/tracks/:

Read conductor/tracks/{trackId}/plan.md:

  • Count total tasks (lines matching - [x], - [~], - [ ] with Task prefix)
  • Count completed tasks ([x])
  • Count in-progress tasks ([~])
  • Count pending tasks ([ ])
  • Identify current phase (first phase with incomplete tasks)
  • Identify next pending task

Read conductor/tracks/{trackId}/metadata.json:

  • Track type (feature, bug, chore, refactor)
  • Created date
  • Last updated date
  • Status

Read conductor/tracks/{trackId}/spec.md:

  • Check for any noted blockers or dependencies

4. Blocker Detection

Scan for potential blockers:

  • Tasks marked with BLOCKED: prefix
  • Dependencies on incomplete tracks
  • Failed verification tasks

Output Format

Full Project Status (no argument)

================================================================================
                        PROJECT STATUS: {Project Name}
================================================================================
Last Updated: {current timestamp}

--------------------------------------------------------------------------------
                              OVERALL PROGRESS
--------------------------------------------------------------------------------

Tracks:     {completed}/{total} completed ({percentage}%)
Tasks:      {completed}/{total} completed ({percentage}%)

Progress:   [##########..........] {percentage}%

--------------------------------------------------------------------------------
                              TRACK SUMMARY
--------------------------------------------------------------------------------

| Status | Track ID          | Type    | Tasks      | Last Updated |
|--------|-------------------|---------|------------|--------------|
| [x]    | auth_20250110     | feature | 12/12 (100%)| 2025-01-12  |
| [~]    | dashboard_20250112| feature | 7/15 (47%) | 2025-01-15  |
| [ ]    | nav-fix_20250114  | bug     | 0/4 (0%)   | 2025-01-14  |

--------------------------------------------------------------------------------
                              CURRENT FOCUS
--------------------------------------------------------------------------------

Active Track:  dashboard_20250112 - Dashboard Feature
Current Phase: Phase 2: Core Components
Current Task:  [~] Task 2.3: Implement chart rendering

Progress in Phase:
  - [x] Task 2.1: Create dashboard layout
  - [x] Task 2.2: Add data fetching hooks
  - [~] Task 2.3: Implement chart rendering
  - [ ] Task 2.4: Add filter controls

--------------------------------------------------------------------------------
                              NEXT ACTIONS
--------------------------------------------------------------------------------

1. Complete: Task 2.3 - Implement chart rendering (dashboard_20250112)
2. Then: Task 2.4 - Add filter controls (dashboard_20250112)
3. After Phase 2: Phase verification checkpoint

--------------------------------------------------------------------------------
                               BLOCKERS
--------------------------------------------------------------------------------

{If blockers found:}
! BLOCKED: Task 3.1 in dashboard_20250112 depends on api_20250111 (incomplete)

{If no blockers:}
No blockers identified.

================================================================================
Commands: /conductor:implement {trackId} | /conductor:new-track | /conductor:revert
================================================================================

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

  1. 2d ago First seen · 320 lines · 10 tokens per session scan A cfd6e838f86b

Subscribe to this mod's changes

status is a command published in the GitHub repository wshobson/agents (39,428 stars, last pushed 3d ago), licensed MIT. It adds 10 tokens to every session and 1,869 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-09-03.