design

A command for preparing product and interface design guidance for changes that affect what users see or do.

In plain words
What is it for?
Documenting interface requirements in 05-design.md, including user flows, information structure, states, interaction notes, accessibility considerations, and Markdown wireframes.
Why use it?
It makes user-flow, layout, copy, accessibility, responsive behavior, and interaction details explicit before implementation.

Command

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 commands/lab94/frenchie-skill/design
Clone the repo
git clone --depth 1 https://github.com/Lab94/frenchie-skill
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 138 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.00000 $0.00138
Opus 5 $0.00000 $0.00069
Sonnet 5 $0.00000 $0.00028
Haiku 4.5 $0.00000 $0.00014

Measured yesterday against content hash 80828957352c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

design 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.

method/commands/design.md · 12 lines

What it actually says

/design

Produce product/UI design guidance for user-facing changes.

Use repository conventions and appropriate design research. Capture user flows, information architecture, states, copy/interaction notes, accessibility considerations, responsive behavior, and Markdown wireframes where useful.

Artifact contract: write or update the canonical 05-design.md. Do not create 03-design.md or renumber design ahead of test cases and implementation planning. Preserve TDD order: test cases live in 03-test-case.md, implementation plan lives in 04-implementation-plan.md, and product/UI design lives in 05-design.md.

Conditional command: required when the task changes user experience.

Alias: /frenchie-design.

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. yesterday First seen · 12 lines · 0 tokens per session scan A 80828957352c

Subscribe to this mod's changes

design is a command published in the GitHub repository Lab94/frenchie-skill (0 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 138 tokens. 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.