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-get-contextgit 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-get-context)<a href="https://agentmods.dev/skills/dkeken/codex-skills-alternative/design-get-context"><img src="https://agentmods.dev/badge/skills/dkeken/codex-skills-alternative/design-get-context/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-get-context"><img src="https://agentmods.dev/badge/skills/dkeken/codex-skills-alternative/design-get-context.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.00101 | $0.00981 |
| Opus 5 | $0.00051 | $0.00491 |
| Sonnet 5 | $0.00020 | $0.00196 |
| Haiku 4.5 | $0.00010 | $0.00098 |
Grade A, and why
design-get-context 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 9d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design — Get Context
De-risk the whole design effort by nailing the brief first. The cheapest fix is the question you ask before building. This skill produces ./design/context.md — the single source of truth every other design skill reads. Skipping it is the #1 cause of "that's not what I meant" rework.
When to use
- Any new design/UI task where the spec isn't already crisp.
- The request is a one-liner ("design a settings page") with implicit, unstated requirements.
- Before
design-research,design-audit,design-ideate, or any build skill.
When NOT to use
- A solid
./design/context.md(or equivalent spec) already exists → proceed to the next skill. - A pure visual-asset task with no UX → that's the Creative Production set.
What to interrogate (ask the gaps, don't dump all at once)
- Goal: what outcome or behavior change is this UI for? (not "a page" — why)
- User: who uses it, their context, tech comfort, frequency.
- Job-to-be-done: the core task the screen must make effortless.
- Constraints: existing stack, design system, brand, platform, deadline.
- Success criteria: how we'll know it worked — ideally measurable.
- Scope: must-have vs nice-to-have for v1; explicit non-goals.
Ask only the questions whose answers would change the design. If something's already given, don't re-ask. If the user can't answer "success criteria", propose 2-3 candidates and let them pick.
Workflow
- Identify the critical unknowns (the ones that would change what you build).
- Ask them concisely, grouped, not as a 20-question interrogation.
- If the user's framing seems flawed (wrong problem, contradictory constraints), raise it and propose an alternative before proceeding.
- Write
./design/context.mdwith answers + explicitly flagged assumptions + risks. - Hand off to
design-research,design-audit, ordesign-ideate.
Output: ./design/context.md
# Context
goal: cut onboarding drop-off (currently 40% abandon at step 2)
user: first-time SaaS trial users, mixed tech comfort, on desktop
JTBD: get to "first value" (a created project) in under 2 minutes
constraints: stack=Next.js + Tailwind DS=internal "Aurora" platform=web deadline=2wk
success: step-2 completion ↑ from 60% → 80%; time-to-first-project < 2min
scope v1: [3-step wizard, skip-able, progress saved]
non-goals: [mobile layout, SSO, team invites]
open assumptions: [users have a use case in mind on arrival]
⚠ risks: [if drop-off is a value problem not a UX problem, redesign won't fix it]
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.
- 9d ago First seen · 67 lines · 101 tokens per session scan A c639ddbe98d4
design-get-context is a skill published in the GitHub repository DKeken/codex-skills-alternative (15 stars, last pushed 3mo ago), licensed MIT. It adds 101 tokens to every session and 981 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…