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 NickCrew/Claude-Cortex --skill design-journey-reviewgit clone --depth 1 https://github.com/NickCrew/Claude-CortexWrote 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/nickcrew/claude-cortex/design-journey-review)<a href="https://agentmods.dev/skills/nickcrew/claude-cortex/design-journey-review"><img src="https://agentmods.dev/badge/skills/nickcrew/claude-cortex/design-journey-review/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/nickcrew/claude-cortex/design-journey-review"><img src="https://agentmods.dev/badge/skills/nickcrew/claude-cortex/design-journey-review.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.00065 | $0.02066 |
| Opus 5 | $0.00032 | $0.01033 |
| Sonnet 5 | $0.00013 | $0.00413 |
| Haiku 4.5 | $0.00006 | $0.00207 |
Grade A, and why
design-journey-review 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 — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design & Journey Review
Combined review of visual design and user journey. Evaluates whether an interface looks coherent and purposeful (color, type, spacing, density, hierarchy) and whether it serves the user's real workflow across sessions (friction points, emotional curve, golden path optimization, information architecture for daily use).
This skill merges the "how does it serve the user?" axis: visual hierarchy, color/type coherence, density balance, workflow stages, emotional patterns, and daily-use friction.
When to Use
- Evaluating visual hierarchy and information density for data-dense UIs
- Reviewing color system coherence (semantic colors, phase colors, theme adaptation)
- Assessing typography choices and type scale effectiveness
- Mapping the user's actual workflow and identifying friction
- Optimizing for daily-driver use cases (expert users, repeated sessions)
- Evaluating whether design choices earn their viewport space
- Finding density inversions (low-value content in high-value positions)
Do NOT use for interaction mechanics (state coverage, feedback timing, escape hatches). Use ux-interaction-review for those.
Quick Reference
| Task | Load reference |
|---|---|
| Visual system evaluation criteria | skills/design-journey-review/references/visual-and-journey-criteria.md |
Workflow
Step 1: Identify the Aesthetic Identity
Before evaluating individual elements, name the aesthetic the interface is targeting. Common archetypes:
- Mission control / operational terminal (dark, data-dense, monospace, status colors)
- Swiss/minimal (clean, lots of white space, geometric, strict grid)
- Linear/GitHub (dark panels, subtle borders, pill chips, blue accent)
- Editorial (large type, serif headings, generous spacing, reading-focused)
- Dashboard/enterprise (card-based, neutral, data visualization heavy)
If the interface doesn't commit to an identity, that's the first finding.
Step 2: Color System Assessment
Evaluate the color architecture:
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 · 240 lines · 65 tokens per session scan A 60d442fba104
design-journey-review is a skill published in the GitHub repository NickCrew/Claude-Cortex (39 stars, last pushed 2mo ago), licensed MIT. It adds 65 tokens to every session and 2,066 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
design-stylecards
Declarative catalog of named aesthetic recipes — exact shadow stacks, glass surfaces, gradient treatments, and type scales as copy-paste values with Use-When and Avoid rules. Use when the user asks for polished elevation, glassmorphism, a border gradient, a mesh background, or any 'make it look like X' request where…
frontend-design
Based on Anthropic's Frontend Aesthetics research. Adapted for OpenClaw with practical tooling additions.
paperclip-capsules
Generate, implement, or review Paperclip capsule visuals. Use for capsule art, agent capsules, heartbeat status capsules, identicons, capsule banks, or brand-usage validation.
ux-design
Guided, section-by-section UX spec authoring for a screen, flow, or HUD. Reads game concept, player journey, and relevant GDDs to provide context-aware design guidance. Produces ux-spec.md (per screen/flow) or hud-design.md using the studio templates.
ux-review
Validates a UX spec, HUD design, or interaction pattern library for completeness, accessibility compliance, GDD alignment, and implementation readiness. Produces APPROVED / NEEDS REVISION / MAJOR REVISION NEEDED verdict with specific gaps.
design-context-extract
Extract design DNA from app screenshots, live URLs, or screen recordings using Google Stitch — color palettes, typography, spacing tokens, component patterns, and motion specs as design-tokens.json or Tailwind config. Use when the user points to a screenshot, URL, or video and asks to extract or audit the design…