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.
git clone --depth 1 https://github.com/clownware/product-devWrote 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.
[](https://agentmods.dev/commands/clownware/product-dev/optimize)<a href="https://agentmods.dev/commands/clownware/product-dev/optimize"><img src="https://agentmods.dev/badge/commands/clownware/product-dev/optimize/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.
<a href="https://agentmods.dev/commands/clownware/product-dev/optimize"><img src="https://agentmods.dev/badge/commands/clownware/product-dev/optimize.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00014 | $0.00278 |
| Opus 5.5 | $0.00006 | $0.00111 |
| Sonnet 5.5 | $0.00003 | $0.00056 |
| Haiku 4.5 | $0.00001 | $0.00028 |
Grade A, and why
optimize 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 1mo 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
Start a reverse-pass UX audit using the ux-optimization skill.
-
If
$ARGUMENTSnames a repository path or product, use it as the audit target. Otherwise ask the user what product to audit — a repo path is the minimum input. -
Read
.product-dev/context.json:- If it doesn't exist, the skill creates a new project with
"mode": "reverse". - If a forward-pass project exists in this directory, confirm before proceeding — the reverse pass writes the same artifact names (
initial_concept,problem_statement,proto_persona,user_flow) and would version over them.
- If it doesn't exist, the skill creates a new project with
-
Ask two setup questions before extraction begins:
- Is the user the product owner (live validation) or a reviewer (deferred validation, flags propagate)?
- Do they have existing tactical feedback to integrate? If yes, save it as the
existing_feedbackartifact first.
-
Hand off to the
ux-optimizationskill for the full sequence: extraction (subagents) → synthesis → validation checkpoint → gap analysis → optimization spec.
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.
- 1mo ago First seen · 23 lines · 14 tokens per session scan A 60bfe98fcd53
optimize is a command published in the GitHub repository clownware/product-dev (3 stars, last pushed 3d ago), licensed Apache-2.0. It adds 14 tokens to every session and 278 once invoked, about $0.0001 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.
Other commands, from other repositories
design-audit
Audit an existing HTML/CSS design. Deterministic checks only (contrast, fonts, colors, states, dark mode) plus a visual pass. No generation.
design-mobile
Design a mobile screen or flow. This command never writes SwiftUI or Compose — the deliverable is a device-framed HTML mockup plus a handoff spec for the platform developer.
design-component
Generate a single component using existing design-system.md tokens. Skips inspiration browsing — fast path for isolated UI elements.
design-page
New page or screen in an existing project. Skips design-system creation — reuses the existing design-system.md tokens.
design
Full design pipeline for a web or web-app target: brief → tokens → generation → motion → review. Use /design:mobile for iOS/Android instead.
dt
Design Thinking mode: /dt toggles, on|off|status set/query, anything else runs as a prompt with mode on.