status

A command that reports the current stage of a structured engineering task, its test information, covered scenarios, and warnings.

In plain words
What is it for?
Use it to check an active task’s progress, test runner, warnings, and next action.
Why use it?
It shows what has been completed and what needs attention without requiring you to inspect task and log files yourself.

Skill for Claude CodeCodex

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 skills/gowtham012/claude-plugins/status
Any agent
npx skills add gowtham012/Claude-plugins --skill status
Clone the repo
git clone --depth 1 https://github.com/gowtham012/Claude-plugins

Made for: Claude Code, Codex.

Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 534 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.00022 $0.00534
Opus 5 $0.00011 $0.00267
Sonnet 5 $0.00004 $0.00107
Haiku 4.5 $0.00002 $0.00053

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

deep-engineer/skills/status/SKILL.md · 67 lines

What it actually says

Current task state (auto-injected)

Task file exists?

!`test -f deep-engineer/current-task.md && echo "YES — active task" || echo "NO — no active task"`

Warning count:

!`grep -c '"warning"' deep-engineer/log.jsonl 2>/dev/null || echo "0"` warnings in log

Instructions

Step 1: Call mcp__deep-engineer__read_task with cwd = current working directory.

If no active task exists, tell the user:

No active task. Start one with /deep-engineer:solve <problem description>.

If a task exists, continue to Step 2.

Step 2: Call mcp__deep-engineer__check_warnings with cwd = current working directory.

Step 3: Call mcp__deep-engineer__detect_test_runner with cwd = current working directory.

Step 4: Format the response:

Active Task Status

Phase: (N of 5)

generalize → hypothetical-testing → tdd-write-tests → implement → verify
     ✓              ✓                    ◀ YOU ARE HERE

Problem (generalized):

Scenarios: defined

Test Runner: <detected command or "not detected">

Warnings:

Phase Log:

Next action:

For the "Next action", be specific:

  • generalize → "List 5+ scenarios and call save_task"
  • hypothetical-testing → "Walk through each scenario mentally, document in a table"
  • tdd-write-tests → "Write test files, run them, confirm all fail"
  • implement → "Write implementation to pass all tests"
  • verify → "Run all tests, fix failures, loop until green"
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 · 67 lines · 22 tokens per session scan A 8c006dadfc89

Subscribe to this mod's changes

status is a skill published in the GitHub repository gowtham012/Claude-plugins (5 stars, last pushed 5mo ago), licensed MIT. It adds 22 tokens to every session and 534 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.