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 oneworks-ai/app --skill ui-design-memorygit clone --depth 1 https://github.com/oneworks-ai/appWrote 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/oneworks-ai/app/ui-design-memory)<a href="https://agentmods.dev/skills/oneworks-ai/app/ui-design-memory"><img src="https://agentmods.dev/badge/skills/oneworks-ai/app/ui-design-memory/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/oneworks-ai/app/ui-design-memory"><img src="https://agentmods.dev/badge/skills/oneworks-ai/app/ui-design-memory.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Memory Poisoning · line 3 Skill injects content designed to persist in agent memory or context across interactions. Persistent injection can alter agent behavior long after the initial interaction.Fix: Do not allow untrusted input to persist in agent memory or context. Validate all content before storing and implement memory isolation between sessions.
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.00107 | $0.01460 |
| Opus 5.5 | $0.00043 | $0.00584 |
| Sonnet 5.5 | $0.00021 | $0.00292 |
| Haiku 4.5 | $0.00011 | $0.00146 |
Grade A, and why
ui-design-memory 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 1mo 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OneWorks UI Design Memory
Use repository files as the team's revisioned, version-controlled design memory. Do not rely on a person, model, or current conversation to preserve standards.
Start every visual task
- Read team-design-standards.md.
- Read
.oo/rules/frontend-standard/design-memory.md, its registry, applicable project design rules, design tokens, shared component guidance, and the nearestAGENTS.md. - Search existing rules before proposing a new standard. Prefer
rgover broad source scans. - Produce a concise Visual Brief before non-mechanical visual edits:
- target surface and viewports;
- reference images or existing product surfaces;
- layout hierarchy and key geometry;
- components and tokens to reuse;
- interaction and responsive invariants;
- prohibited patterns;
- expected user behaviors;
- required screenshots and observable checks.
- host chrome ownership: which existing header, sidebar, breadcrumb, and action slot already names or navigates the current object.
- Keep task-specific coordinates and temporary adjustments in the Visual Brief, not durable memory.
Before adding a visible title, breadcrumb, navigation button, refresh command, or outer padding, inspect the complete host surface. Do not duplicate a title already owned by the route header, place collection navigation in object-level header actions, add manual refresh when the data layer already revalidates, or let both the host and embedded view own the same inset. Prefer the host's existing sidebar action, breadcrumb, header action, and data-query contracts.
Classify user feedback
Treat feedback as a durable-standard candidate when it uses normative language such as all, always, default, must, ensure, standard, consistent, 统一, 所有, 以后, 默认, 始终, 必须, 保证, 规范, or 不要再.
Treat feedback as task-local when it only adjusts the current composition, for example move this 2px left, crop this image slightly, or use x=278 for this reference viewport.
What ships with it
4 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.
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.
- 1mo ago First seen · 102 lines · 107 tokens per session scan A 778fb95d22d1
ui-design-memory is a skill published in the GitHub repository oneworks-ai/app (20 stars, last pushed 1mo ago), licensed MIT. It adds 107 tokens to every session and 1,460 once invoked, about $0.0004 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-08-30.
Other skills, from other repositories
a11y-audit
Run a Maestro-style accessibility audit for WCAG compliance, ARIA usage, keyboard navigation, and screen reader compatibility.
lov-maintain-partners
Maintain the Skill Publisher website's partners section AND align partner logo rows on event posters / hero strips: reuse lov-find-logo for brand logo discovery, normalize collected logos to a 240px-tall content canvas (retina-ready), rasterize SVGs via rsvg-convert before normalizing (so SVG viewBox padding gets…
lov-oh-my-landingpage
A landing-page creation and redesign skill that derives a product’s positioning, story, and visual direction from its actual product and brand facts. It then implements the page responsively and checks the result against the intended product message.
lov-frontend-design
A frontend design guide for turning requirements, existing screens, and real media into usable pages and components. It covers visual design, navigation, interaction details, animation, images, audio, and video.
lov-install-shadcn-ui
A setup tool for shadcn/ui, a collection of editable interface components for web projects. It installs only needed pieces and adapts their styles to the project’s existing theme and Tailwind version.
lov-install-web-logo
A website branding tool that connects an approved logo to browser icons, the web app manifest, page metadata, and related components. A favicon is the small icon shown in a browser tab; a PWA manifest describes an installable web app.