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 commands/clownware/product-dev/problemgit 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.00008 | $0.00259 |
| Opus 5 | $0.00004 | $0.00130 |
| Sonnet 5 | $0.00002 | $0.00052 |
| Haiku 4.5 | $0.00001 | $0.00026 |
Grade A, and why
problem 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 yesterday.
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
Start a problem definition session using the product-ideation skill, entering at Phase 01.
Setup
-
Check
.product-dev/context.jsonfor existing project state.- If
initial_conceptartifact exists, read it — this is input for the problem statement. - If no project exists, create one and note that we're starting at problem definition without prior exploration.
- If
-
If
$ARGUMENTSprovided, use it as the starting context alongside any existinginitial_concept. -
Read
${CLAUDE_PLUGIN_ROOT}/prompts/01_ux_research/01_define_problem/01_create_problem_statement.md. -
Resolve
{{initial_concept}}from the registry or from user input. -
Execute the prompt. Write
problem_statementartifact to.product-dev/artifacts/problem_statement.mdand update registry. -
Continue the
product-ideationskill flow from Phase 01:create_proto_persona→identify_core_objective→generate_solution_concept→format_hypothesis_statement.
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.
- yesterday First seen · 27 lines · 8 tokens per session scan A fbc08c3c8b7c
problem is a command published in the GitHub repository clownware/product-dev (3 stars, last pushed 5d ago), licensed Apache-2.0. It adds 8 tokens to every session and 259 once invoked, about $0.0000 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 commands, from other repositories
start
Front door. Reads the current project (framework, tokens, brief, spec, harness) and reports what ui-craft can do right now, then routes you to the right next step. Run this first if you're new or unsure where to begin. No code changes.
tokens
Audit or establish the project's 3-layer token spine.
remember
Record a learned design constraint from a correction into the project brief.
craft
One-shot build pipeline for a complete surface from an outcome recipe — inputs (or defaults) → composition → theme → build order → acceptance bar. Use when the user asks for a whole surface ("build me a dashboard", "I need a landing page") and expects a shippable result, not component-level help.
audit
Technical UI audit — a11y, performance, responsive. Produces a prioritized findings table.
brief
Write or update the project's durable design brief at .ui-craft/brief.md.