status

A status view for a product-development project stored in the current working folder. It shows progress through research, design, prototyping, and technical-planning stages.

In plain words
What is it for?
Use it to check the project name, progress, dates, available documents, and suggested next actions.
Why use it?
It removes the need to inspect project files manually to know what has been completed. It also points to likely next steps when work is unfinished.

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

Made for: Claude Code, Codex.

Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 532 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.00024 $0.00532
Opus 5 $0.00012 $0.00266
Sonnet 5 $0.00005 $0.00106
Haiku 4.5 $0.00002 $0.00053

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

plugin/skills/status/SKILL.md · 52 lines

What it actually says

Display the current product development project status. This is primarily deterministic — no LLM generation needed for core display. Canonical display format and staleness rule: ${CLAUDE_PLUGIN_ROOT}/docs/registry-operations.md § Status Display.

Execution

  1. Read .product-dev/context.json from the working directory.

  2. If no project exists:

    "No product development project found in this directory. Run /product-dev:idea to start one."

  3. If project exists, display:

Project: {project_name}
Tier: {tier} ({tier_label})
Started: {created}
Last updated: {updated}

Phase Progress:
  00 Fuzzy Front End       [{completed}/{total}] {progress_bar}
  01 Define Problem        [{completed}/{total}] {progress_bar}
  02 Objectives            [{completed}/{total}] {progress_bar}
  03 Solution Hypothesis   [{completed}/{total}] {progress_bar}
  04 User Flow             [{completed}/{total}] {progress_bar}
  05 Prototype             [{completed}/{total}] {progress_bar}
  06 Post-Test Synthesis   [{completed}/{total}] {progress_bar}
  Tech Requirements        [{completed}/{total}] {progress_bar}

Artifacts:
  {name}  (from {source_prompt}, {date}){staleness}
  ...

Suggested Next:
  {list prompts whose `requires` are all satisfied by existing artifacts}

{staleness}: compare each artifact's inputs map (input artifact name → version recorded at generation) against those artifacts' current version fields. If any recorded version is lower, append [stale: {input} v{recorded} → v{current}]. Omit for fresh artifacts and for entries with no inputs map (pre-provenance projects). If any artifact is stale, add one line after the artifact list: "Stale artifacts were built from older inputs — regenerate via their source prompts."

  1. Tier labels: 1 = "Quick Exploration", 2 = "Structured Discovery", 3 = "Full Framework".

  2. Count only prompts matching the current tier level for progress calculations.

  3. For suggested next steps, check each unexecuted Tier 1 prompt's requires array against existing artifacts. List those that are unblocked.

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 · 52 lines · 24 tokens per session scan A 9fad3c8f9a25

Subscribe to this mod's changes

status is a skill published in the GitHub repository clownware/product-dev (3 stars, last pushed 6d ago), licensed Apache-2.0. It adds 24 tokens to every session and 532 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.