status

status is a command for Claude Code from FunkyOz/funkyoz-plugins. It costs 10 tokens per session (916 once invoked), scanned A, original, MIT.

A command that reports the progress of development tasks by reading task files and their statuses. It can show either a summary or more detailed task information.

In plain words
What is it for?
Use it to view overall progress, completed and unfinished work, current focus, or detailed task descriptions.
Why use it?
It removes the need to inspect each task file manually to understand what is finished, underway, or still waiting.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: model in frontmatter.

Part of the software-engineer plugin — 1 skill, 4 commands, 2 agents shipped together

Good fit Use it to view overall progress, completed and unfinished work, current focus, or detailed task descriptions.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/funkyoz/funkyoz-plugins/status
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.

Clone the repo
git clone --depth 1 https://github.com/FunkyOz/funkyoz-plugins

Made for: Claude Code.

Or install software-engineer, the plugin that ships this one along with the rest of its 1 skill, 4 commands, 2 agents.

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/funkyoz/funkyoz-plugins/status/github.svg)](https://agentmods.dev/commands/funkyoz/funkyoz-plugins/status)
Your own site
<a href="https://agentmods.dev/commands/funkyoz/funkyoz-plugins/status"><img src="https://agentmods.dev/badge/commands/funkyoz/funkyoz-plugins/status/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for status

Your own site · 80×15
<a href="https://agentmods.dev/commands/funkyoz/funkyoz-plugins/status"><img src="https://agentmods.dev/badge/commands/funkyoz/funkyoz-plugins/status.svg" alt="Reviewed on agentmods" width="80" 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 916 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00010 $0.00916
Opus 5.5 $0.00004 $0.00366
Sonnet 5.5 $0.00002 $0.00183
Haiku 4.5 $0.00001 $0.00092

Measured 2mo ago against content hash 4078cf5aaed6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 2mo 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.

software-engineer/commands/status.md · 123 lines

How it starts

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

Status Command

You are reporting on the current progress of the development tasks.

Input

  • Argument: {{1}}
    • (empty) - Show summary status
    • detailed - Show detailed status with task descriptions

Process

Step 1: Load Task Data

  1. Read the tasks/00-index.md file
  2. Read all individual task files (tasks/XX-*.md)
  3. Parse the YAML frontmatter from each task to get current status

If no tasks/ directory exists:

"No task breakdown found. Run /software-engineer:plan <feature description> to create a development plan."

Step 2: Calculate Progress

Compute the following metrics:

  • Total tasks: Count of all task files (excluding 00-index.md)
  • Completed: Tasks with status: done
  • In Progress: Tasks with status: progress
  • Todo: Tasks with status: todo
  • Progress percentage: (Completed / Total) × 100

Step 3: Display Status

Summary View (default)
📊 Development Progress
═══════════════════════════════════════════════════════

Progress: [████████████░░░░░░░░] 60% (12/20 tasks)

✅ Completed:    12 tasks
🔄 In Progress:   2 tasks
📋 Todo:          6 tasks

───────────────────────────────────────────────────────

Current Focus:
  → Task 13: [Task Title] (progress)
  → Task 14: [Task Title] (progress)

Next Up:
  → Task 15: [Task Title] (Priority: High)
  → Task 16: [Task Title] (Priority: Medium)

───────────────────────────────────────────────────────

Phase Progress:
  Phase 1: Foundation       ████████████████████ 100% ✓
  Phase 2: Core             ████████████████░░░░  80%
  Phase 3: Advanced         ░░░░░░░░░░░░░░░░░░░░   0%
  Phase 4: Testing          ████████░░░░░░░░░░░░  40%

═══════════════════════════════════════════════════════
Detailed View (with detailed argument)

Include all the above, plus:

───────────────────────────────────────────────────────
📋 All Tasks
───────────────────────────────────────────────────────

Phase 1: Foundation
  ✅ 01. Project Setup (done) - Low complexity
  ✅ 02. Config Constants (done) - Low complexity
  ✅ 03. Exception Classes (done) - Low complexity

Phase 2: Core Implementation
  ✅ 04. Buffer Manager (done) - Medium complexity
  🔄 05. Lexer/Tokenizer (progress) - High complexity
       ↳ Dependencies: Tasks 03, 04 ✓
       ↳ Acceptance: 3/5 criteria met
  📋 06. Streaming Parser (todo) - High complexity
       ↳ Dependencies: Tasks 02, 03, 05 (waiting on 05)

[... continue for all tasks ...]

───────────────────────────────────────────────────────
🚧 Blockers & Issues
───────────────────────────────────────────────────────

• Task 05 is blocking tasks 06, 07, 08
• No critical issues reported

───────────────────────────────────────────────────────

Read the full file on GitHub · 123 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. 2mo ago First seen · 123 lines · 10 tokens per session scan A 4078cf5aaed6

Subscribe to this mod's changes

status is a command published in the GitHub repository FunkyOz/funkyoz-plugins (2 stars, last pushed 10mo ago), licensed MIT. It adds 10 tokens to every session and 916 once invoked, about $0.0000 per session on Opus 5.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.