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.
npx agentmods add skills/clownware/product-dev/statusnpx skills add clownware/product-dev --skill statusgit clone --depth 1 https://github.com/clownware/product-devWhat 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.00024 | $0.00532 |
| Opus 5 | $0.00012 | $0.00266 |
| Sonnet 5 | $0.00005 | $0.00106 |
| Haiku 4.5 | $0.00002 | $0.00053 |
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.
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
-
Read
.product-dev/context.jsonfrom the working directory. -
If no project exists:
"No product development project found in this directory. Run
/product-dev:ideato start one." -
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."
-
Tier labels: 1 = "Quick Exploration", 2 = "Structured Discovery", 3 = "Full Framework".
-
Count only prompts matching the current tier level for progress calculations.
-
For suggested next steps, check each unexecuted Tier 1 prompt's
requiresarray against existing artifacts. List those that are unblocked.
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 · 52 lines · 24 tokens per session scan A 9fad3c8f9a25
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.
Other skills, from other repositories
feature-flags
Use when feature flag tests fail, flags need updating, understanding @gate pragmas, debugging channel-specific test failures, or adding new flags to React.
frontend-unit-testing
Write comprehensive, behaviour-driven unit tests for Gradio frontend Svelte components using Vitest browser mode, Playwright, and the @self/tootils test utilities.
gradio-themes
Build and customise Gradio themes. Use when creating, editing, or publishing Python-based Gradio themes that control colours, typography, spacing, shadows, and dark mode.
hf-gradio
Use Gradio applications via API. Use when the user asks for to generate a prediction from a Gradio app on Hugging Face spaces or public URL. For example, "Generate an image using black-forest-labs/FLUX.2-dev".
compiler-port
Port a compiler pass from TypeScript to Rust. Gathers context, plans the port, implements in a subagent with test-fix loop, then reviews.
flags
Use when you need to check feature flag states, compare channels, or debug why a feature behaves differently across release channels.