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 dkstm95/hope --skill designgit clone --depth 1 https://github.com/dkstm95/hopeWrote 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/dkstm95/hope/design)<a href="https://agentmods.dev/skills/dkstm95/hope/design"><img src="https://agentmods.dev/badge/skills/dkstm95/hope/design/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/dkstm95/hope/design"><img src="https://agentmods.dev/badge/skills/dkstm95/hope/design.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.00022 | $0.01327 |
| Opus 5.5 | $0.00009 | $0.00531 |
| Sonnet 5.5 | $0.00004 | $0.00265 |
| Haiku 4.5 | $0.00002 | $0.00133 |
Grade A, and why
design 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 today.
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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hope Design
Use only when the person invokes $hope:design, /hope:design, or the
host's equivalent skill command or picker. Continue follow-ups within that
invoked task without requiring another invocation. Ordinary requests and calls
from another skill do not activate this skill; continue authorized work through
the ordinary workflow. Reading a shared reference does not invoke its skill.
Turn the person's purpose and impressions into a considered interface they can see, try, and direct. Carry new screens, refinements, reference studies, or comparisons through the requested result. Preserve settled choices, the parts the person likes, and existing implementation authorization.
Read ../write/references/writing-standard.md for language and
references/judgment.md for design judgment. Use the topic references below
when they affect the current work; do not read the whole library on every run.
Establish what this work needs
Read the conversation, actual screens, representative code and content, design rules, components, and assets. A coherent existing interface is a design system even without a DESIGN.md. Distinguish a local refinement, a new surface inside that system, and a requested redesign. Preserve the corresponding scope.
Understand who uses the screen, what they need to accomplish, and where it fits in their work. Investigate what the environment can answer. Ask only unresolved questions that change the result, in terms of actions and consequences rather than CSS values or style names. Use visual evidence when words cannot settle a visual choice. Follow existing decisions and delegation; a request to make a mockup does not itself choose a material product trade-off.
An impression is a clue, not a prescription. For "cramped," inspect grouping,
density, reading width, and navigation effort before adding space. For "bland,"
inspect composition and emphasis before adding effects. Explain the likely
cause through the person's task. Read references/exploration.md when direction,
reference interpretation, or feedback needs work.
What ships with it
11 files 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.
- agents/openai.yaml 297 B
- LICENSE.emil 1.0 KB
- LICENSE.impeccable 11 KB
- LICENSE.interface-design 1.0 KB
- LICENSE.jakub 1.0 KB
- references/continuity.md 3.1 KB
- references/exploration.md 4.1 KB
- references/judgment.md 3.9 KB
- references/prototypes.md 4.2 KB
- references/sources.md 5.1 KB
- references/verification.md 4.1 KB
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.
- today Changed · -2 lines 6391ac9b48c6
- 1mo ago Changed · +9 lines · -18 tokens per session 47c49a62df60
- 1mo ago First seen · 113 lines · 40 tokens per session scan A b4aa4c68aefd
design is a skill published in the GitHub repository dkstm95/hope (8 stars, last pushed today), licensed MIT. It adds 22 tokens to every session and 1,327 once invoked, about $0.0001 per session on Opus 5.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-13.
Other skills, from other repositories
figma-design-system-to-design-md
Figma design system to design.md — Extract Figma design system into a structured design.md. Use when user says 'generate design.md', 'extract design system', 'design tokens to markdown', 'create design doc from Figma', 'Figma design system to design.md', or wants to document their design system from token files and…
chartware
Generate enterprise-grade diagrams and data charts in three media — Mermaid (text-first diagrams), hand-authored inline SVG (pixel-perfect charts and figures for HTML embedding), and draw.io via the drawio MCP (editable diagram artifacts) — with a curated visual style system wired to the plugin's brand registry. Use…
a11y-audit
Dedicated WCAG 2.2 AA/AAA accessibility audit across 10 dimensions (A1-A10) covering semantic HTML, keyboard navigation, ARIA patterns, color contrast, forms, images/media, responsive/zoom, motion/animation, reading/content, and legal compliance. Goes far beyond surface-level design-review checks with deep…
design-review
UI/UX design consistency audit. Code-based DX1-DX20 checklist covering states, consistency, accessibility, responsive behavior, and interaction patterns. Optional visual audit via chrome-devtools screenshots and automated WCAG accessibility via axe-core. DAP1-DAP12 anti-pattern detection. Modes: [path], visual…
design
Intent-first UI design with conscious, traceable design decisions. Persists decisions in .interface-design/ for cross-session consistency. Includes domain exploration, design system generation (system.md + system.json), per-component construction with mandatory checkpoints, and craft validation tests. Modes: init…
ui-design-team
Multi-agent UI review with 4 specialist perspectives: UX Researcher, Visual Designer, i18n/Multilingual QA, and Accessibility/Performance Auditor. Each agent scores independently from their expertise. Lead Designer synthesizes into prioritized fixes with exact code. Works with any stack: React, Astro, vanilla…