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 agentmods add skills/lenxism/ives/style-directionnpx skills add lenxism/ives --skill style-directiongit clone --depth 1 https://github.com/lenxism/ivesWrote 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/lenxism/ives/style-direction)<a href="https://agentmods.dev/skills/lenxism/ives/style-direction"><img src="https://agentmods.dev/badge/skills/lenxism/ives/style-direction.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 | $0.00104 | $0.01053 |
| Opus 5 | $0.00052 | $0.00526 |
| Sonnet 5 | $0.00021 | $0.00211 |
| Haiku 4.5 | $0.00010 | $0.00105 |
Grade A, and why
style-direction 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 4d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Style & Direction
Style is about art direction — how you want your designs to feel. Every visual choice (radius, shadow, border, opacity) communicates personality.
Design Direction
Before choosing any visual treatments, define what you're going for:
- What adjectives describe the desired feel? (Bold, calm, playful, technical, luxury)
- What existing products share this energy?
- What typeface style fits? (Serif = established, geometric sans = modern, humanist = friendly)
Design a few key components in different directions before committing. The same layout in four different typefaces and color schemes can feel completely different.
Subtlety
The difference between amateur and professional design is often subtlety:
- Shadows that are barely visible but create depth
- Hover states that shift 5% rather than 50%
- Color differences between sections of 2-3% brightness, not 20%
- Transitions at 200-300ms, not 500ms+
If a visual treatment is the first thing you notice, it's probably too strong. The best treatments are felt, not seen.
Corner Radius as Personality
Corner radius is a spectrum from technical to friendly:
- 0-4px — Sharp, precise, authoritative, technical
- 8-12px — Balanced, modern, approachable (most common)
- 16-20px — Soft, friendly, contemporary
- Full rounding — Playful, conversational, pill-shaped
Mixing: Fully rounded buttons and pills for friendliness + medium radius on content cards is a valid strategy. Sharp icons inside rounded containers create balanced tension.
Consistency: Whatever you choose, apply it systematically. Mixed radii without intention looks accidental.
Borders
- Borders add visual weight. The thinner, the better (1px is usually sufficient).
- Use borders consistently or not at all within a section.
- Consider whether spacing alone creates sufficient separation — often it does.
- On dark backgrounds, borders become much more visible. Reduce opacity or eliminate.
- Border color should be a very light gray from your gray system, not a random value.
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.
- 4d ago First seen · 115 lines · 104 tokens per session scan A 7ac876fd920f
style-direction is a skill published in the GitHub repository lenxism/ives (5 stars, last pushed 6mo ago), licensed MIT. It adds 104 tokens to every session and 1,053 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-31.
Other skills, from other repositories
hallmark
Anti-AI-slop design skill for greenfield pages, audits, redesigns, and design extraction from URLs or screenshots. Use when the user asks to build a new app or landing page, wants to redesign something, invokes Hallmark by name, or uses audit/redesign/study.
accessibility
Consolidated accessibility skill entrypoint for WCAG 2.2, ARIA Authoring Practices, cognitive accessibility, Section 508, EN 301 549, design intent verification, and the Accessibility Planner workflow.
desktop-principles
Desktop-specific UX principles - hover states, pointer precision, keyboard shortcuts, multi-window, focus management. Covers macOS, Windows, Linux, web desktop.
taiyi-ui-design
TaiyiForge 第 4 阶段 — UI/UX 契约，产出 UI-DESIGN.md。四端通用。.
accessibility-analysis
服務可達性分析工具箱（accessibility / service coverage）。當用戶說「30km 路網可達」「最近 X 站」「服務範圍」「沙漠」「孤島」「等時圈」「isochrone」「可達性分析」「路網覆蓋」或要新增任何「離 POI 多遠」類型的分析時觸發。整合 mini-taiwan-pulse + taipei-gis-analytics 兩端 SOP，覆蓋三種視覺模式（路網染色 / Polygon 沿路網 / Hex 格點）、三套既有 reference pipeline 對照、模式選擇決策樹、常見坑（Overpass mirror 不穩 / pyrosm 爆 RAM / multi-bucket /…
ui-design
UI 样式修改协作流程（已有界面的视觉层微调）。触发硬条件：页面已经在代码里跑着，改的只是它的视觉表现——布局、间距、颜色、字号、圆角、组件搭配。通过"读代码 + ASCII 画出现状让用户确认 → 给 2-3 个 ASCII 方案 → 用户选定 → 最小改动 → 微调"的流程，减少沟通偏差、避免浪费 token。产出：只动样式的代码 diff。硬边界：不动业务逻辑、不动数据流、不改交互行为、不顺手重构。不适用于：界面还不存在、要从零探索长什么样（用 design-exploration）、改的是功能或交互逻辑而不只是视觉（用 req-change-workflow）、照着设计图/截图复刻整页（用…