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 skills add ommakes/Skills --skill design-askgit clone --depth 1 https://github.com/ommakes/SkillsWrote 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/skills/ommakes/skills/design-ask)<a href="https://agentmods.dev/skills/ommakes/skills/design-ask"><img src="https://agentmods.dev/badge/skills/ommakes/skills/design-ask.svg" alt="Measured on agentmods" 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.00197 | $0.01450 |
| Opus 5 | $0.00098 | $0.00725 |
| Sonnet 5 | $0.00039 | $0.00290 |
| Haiku 4.5 | $0.00020 | $0.00145 |
Grade A, and why
design-ask 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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Ask
Helps designers cut through poorly written tickets to understand what design work is actually being asked for, what's missing, and what questions to ask before starting.
Your job
When a designer pastes in a ticket, you are not designing anything. You are doing triage. Your job is to surface:
- What the ticket is actually asking for
- What's missing or ambiguous
- Whether the ticket is prescribing a solution instead of describing a need
- What design work is required and at what scope
- What questions the designer should ask before touching anything
Be direct. Don't pad the output. If something is unclear, say it's unclear. If a ticket is underbaked, call it that.
Output format
Always produce output in this exact structure. Use the headers as written.
The real ask
In 2-3 sentences, describe what the user or business actually needs here — stripped of implementation language. Ignore any prescribed UI solutions for now. If the ticket is so vague you can't determine this, say so clearly and explain what's missing.
Type of design work
Pick the most accurate category and explain briefly why. If multiple apply, list them in order of likely effort.
- Content only — Labels, copy, error messages, tooltips. No structural change.
- Single screen / state — One view needs to be added or significantly changed.
- Linear flow — Multiple steps, no branching or conditions.
- Branching flow — Two or more paths, conditional logic, or decision points.
- System / pattern — A new component, interaction pattern, or behavior that will recur across the product.
- Unclear — Not enough information to determine scope.
Also answer: Should multiple design variants be explored before committing to one direction? Give a yes/no and a reason.
Known requirements
List only what is explicitly stated in the ticket. These are things the designer should treat as constraints until told otherwise. Keep this tight — if it's not in the ticket, it doesn't go here.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 156 lines · 197 tokens per session scan A 764c0453441f
design-ask is a skill published in the GitHub repository ommakes/Skills (20 stars, last pushed 9d ago), licensed MIT. It adds 197 tokens to every session and 1,450 once invoked, about $0.0010 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-30.
Other skills, from other repositories
refine-live
In-chat fallback for the Timeline Inspector Refine agent. Use when the user runs /refine live, asks to "refine live", "go live", or answer refine jobs — but ONLY when no persistent agent is wired (no npx transitions-refine live). Prefer npx transitions-refine live for run-and-forget (relay spawns agent per click, no…
transitions-dev
Production-ready CSS transitions for web apps. Use when implementing notification badges, dropdowns, modals, panel reveals, page transitions, card resizes, number pop-ins, text swaps, icon swaps, success checks, avatar group hovers, error state shakes, search/input clear, skeleton loaders, shimmer text, sliding tabs…
transitions-polish
Polish and refine existing motion against the transitions.dev motion-token scale — duration, distance, scale, blur, and easing — plus the rules for WHEN each token applies (open/close asymmetry, hover-in vs hover-out, stagger offsets, and intent delays). An add-on to the transitions-dev skill, focused on tuning what…
analog-design-standards
Portable product design standards for creating, reviewing, or refactoring app UI/UX, especially AI-built web apps, dashboards, CRM surfaces, operational workflows, Home screens, AI chat, command surfaces, artifacts, landing pages, and design-system docs. Use when asked to design, build, critique, improve, or set…
design-critique
Give a structured product design critique — user job clarity, hierarchy, affordance, error states, accessibility, and consistency — focused on what to change, in what order, and why.
design-dna
Extract, define, and apply design DNA across three dimensions: design system (tokens), design style (qualitative feel), and visual effects (Canvas, WebGL, 3D, particles, shaders, scroll effects, etc.). Use this skill when: (1) a user wants to see the full 3-dimension design structure/schema, (2) a user provides…