brief

brief is a command for Codex from alwkala/tidyfactor-design. It costs 0 tokens per session (1,281 once invoked), scanned A, original, MIT.

A design-context check for defining an interface’s audience, purpose, tone, and visual direction before building it.

In plain words
What is it for?
Use it to clarify design goals before creating pages, dashboards, or components, or after studying a reference design.
Why use it?
It prevents vague requests from producing generic designs that do not suit the people using them.

Command for Codex

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/alwkala/tidyfactor-design/brief
Clone the repo
git clone --depth 1 https://github.com/alwkala/tidyfactor-design

Made for: Codex.

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

agentmods badge for brief

README.md
[![agentmods](https://agentmods.dev/badge/commands/alwkala/tidyfactor-design/brief.svg)](https://agentmods.dev/commands/alwkala/tidyfactor-design/brief)
Your own site
<a href="https://agentmods.dev/commands/alwkala/tidyfactor-design/brief"><img src="https://agentmods.dev/badge/commands/alwkala/tidyfactor-design/brief.svg" alt="Measured on agentmods" height="20"></a>
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 1,281 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.01281
Opus 5 $0.00000 $0.00641
Sonnet 5 $0.00000 $0.00256
Haiku 4.5 $0.00000 $0.00128

Measured 5d ago against content hash 37c11e2ddbb9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

brief 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 5d 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.

.agents/skills/tidyfactor-design/references/commands/brief.md · 108 lines

How it starts

The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Command: brief — Design Context Gate & Fit Test

Runtime entry point for establishing design context before any build begins. Part of the Discovery lifecycle phase.

When to use

  • Always before init, page, dashboard, or components — the brief ensures the design has intention, not defaults.
  • After study if a reference was analyzed.
  • Whenever a design request lacks context ("build me a landing page" without audience/tone/purpose).

The 3-Question Design-Context Gate

Question 1: Audience

Who is the primary audience, and what is their emotional state when they arrive?

Why it matters: A B2B decision-maker comparing vendors arrives in evaluate mode (needs tables, specs, trust signals). A luxury buyer arrives in aspire mode (needs atmosphere, restraint, desire). The same "landing page" requires completely different design DNA.

Classify into:

Mode Characteristics Design implications
Inspire Browse, dream, aspirate Atmospheric, generous whitespace, cinematic motion, minimal text
Evaluate Compare, decide, justify Data-forward, specs tables, social proof, clear pricing
Act Purchase, sign up, convert Friction-free, prominent CTA, trust signals, minimal distraction
Learn Study, explore, understand Content-rich, good typography, navigation, readable hierarchy

Question 2: Use Case / Surface Type

What kind of surface is this?

Surface Layout suggestions Foundation fit
Marketing landing page film, story, minimal (from memory/13-layout-archetypes.md) native, tailwind
Product / e-commerce product, store tailwind, daisyui
Dashboard / app screen Use dashboard command native, shadcn
Documentation / content Use page command with editorial school native, pico
Real estate / spatial space tailwind
Personal brand / portfolio creator native, pico

Question 3: Tone / Design School

What emotional register should the design communicate?

Read the full file on GitHub · 108 lines

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. 5d ago First seen · 108 lines · 0 tokens per session scan A 37c11e2ddbb9

Subscribe to this mod's changes

brief is a command published in the GitHub repository alwkala/tidyfactor-design (5 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,281 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.