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 DKeken/codex-skills-alternative --skill design-researchgit clone --depth 1 https://github.com/DKeken/codex-skills-alternativeWrote 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/dkeken/codex-skills-alternative/design-research)<a href="https://agentmods.dev/skills/dkeken/codex-skills-alternative/design-research"><img src="https://agentmods.dev/badge/skills/dkeken/codex-skills-alternative/design-research/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/skills/dkeken/codex-skills-alternative/design-research"><img src="https://agentmods.dev/badge/skills/dkeken/codex-skills-alternative/design-research.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.00096 | $0.00907 |
| Opus 5 | $0.00048 | $0.00453 |
| Sonnet 5 | $0.00019 | $0.00181 |
| Haiku 4.5 | $0.00010 | $0.00091 |
Grade A, and why
design-research 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 10d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design — Research
Gather outside signal before inventing. Know the conventions users already expect (so you don't fight muscle memory) and the pains competitors leave on the table (so you can win on them). Good research turns "I think" into "users expect / competitors fail at".
When to use
- Designing a flow that others have solved (auth, onboarding, checkout, settings, dashboards).
- You need to know the convention before deciding whether to follow or break it.
- Looking for differentiation — where do incumbents frustrate users?
- Before
design-ideate, to ground directions in evidence.
When NOT to use
- The brief isn't clear yet →
design-get-contextfirst. - You're critiquing an existing UI of your own →
design-audit. - The pattern is trivial/obvious and research adds nothing — don't over-research.
Inputs
./design/context.md(goal, user, JTBD) if it exists.- The specific flow/feature in question.
Workflow
- Convention scan: what's the established pattern for this flow? Users carry expectations (e.g. cart icon top-right, primary action bottom-right of a form). Deviating has a cost — only do it with a reason.
- Competitor scan: pick 3-5 relevant products. Use a web-search / web-fetch tool (or browser automation) to see how each handles the flow. Capture concrete notes + screenshots.
- Pain mining: search reviews, forums, "X alternative", complaint threads. Where do incumbents frustrate users? Those are your openings.
- Synthesize into three buckets: pains (to solve), patterns (to adopt), gaps (to exploit).
- Write
./design/research.mdand hand todesign-ideate.
Output: ./design/research.md
flow: SaaS checkout / upgrade
conventions (users expect):
- plan comparison table, current plan highlighted
- annual/monthly toggle with "save X%"
- card form: number → expiry → CVC, inline validation
competitors:
- Linear: single-screen upgrade, no modal maze (note: feels fast)
- Notion: plan grid + per-seat math shown live (note: transparent)
- Figma: hides downgrade, dark-patterny (note: AVOID)
pains found (from reviews/forums):
- "couldn't tell what I'd be charged" (surprise totals)
- "had to talk to sales to see pricing" (friction)
opportunities:
- show exact charge before confirm; no sales gate; live proration
sources: [urls...]
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.
- 10d ago First seen · 68 lines · 96 tokens per session scan A 03a25ee6adae
design-research is a skill published in the GitHub repository DKeken/codex-skills-alternative (15 stars, last pushed 3mo ago), licensed MIT. It adds 96 tokens to every session and 907 once invoked, about $0.0005 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
create-chatgpt-mockup
Render pixel-accurate ChatGPT mobile (iOS) screen mockups in light mode from a thread JSON. Supports user text bubbles, user image attachments, assistant markdown prose, citation chips, the OpenAI spiral logo, the Apps-SDK GPT chip in the composer, and three header styles (model-tag, plain title, "Get Plus"). Fixed…
vercel-composition-patterns
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.
ui-designer/design-system
A shared set of rules for a product’s visual design, covering colors, fonts, spacing, corner shapes, shadows, and animations.
layout-skill
Layer A layout-mechanics reference. Stacks on any style skill when the screen is an app shell, dashboard, settings, list-detail, mail/inbox, or any layout with fixed regions plus a scrolling body — or when a layout breaks under long, empty, or unbroken content. Owns spatial structure and scroll ownership; owns zero…
web-artifacts-builder
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
baoyu-design
Create polished design artifacts as self-contained HTML: UI mockups, interactive prototypes, wireframes, landing pages, dashboards, app screens, mobile apps, slide decks (a.k.a. PPT / PowerPoint presentations), documents and résumés, animations, 3D objects, research reports, HTML email, diagrams, fliers, and visual…