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/ohad6k/emulo/designnpx skills add ohad6k/emulo --skill designgit clone --depth 1 https://github.com/ohad6k/emuloWrote 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/ohad6k/emulo/design)<a href="https://agentmods.dev/skills/ohad6k/emulo/design"><img src="https://agentmods.dev/badge/skills/ohad6k/emulo/design.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.00046 | $0.00183 |
| Opus 5 | $0.00023 | $0.00092 |
| Sonnet 5 | $0.00009 | $0.00037 |
| Haiku 4.5 | $0.00005 | $0.00018 |
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 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.
What it actually says
Emulo design
- Locate
emulo.pytwo directories above this skill; fall back to./emulo.pyonly for a direct repo checkout. - Store the resolved absolute runtime path as
EMULO_PY, then runpython "$EMULO_PY" plugin profile-path --domain design. - If it exits nonzero, give its exact recovery or targeted-deepen instruction and stop loading personal context.
- Read every returned path completely. The first is the core working profile; the second is the design profile. Apply both.
- Never substitute a generic design persona when the design domain is inactive.
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 · 13 lines · 46 tokens per session scan A a62ec6d191c2
design is a skill published in the GitHub repository ohad6k/emulo (287 stars, last pushed 10d ago), licensed MIT. It adds 46 tokens to every session and 183 once invoked, about $0.0002 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
impeccable
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states.…
frontend-design
Designs, builds, or refactors user-facing web or application interfaces with deliberate visual direction, typography, color and spacing tokens, content hierarchy, responsive behavior, accessible interaction states, and real rendered-surface verification. Use for pages, components, dashboards, landing pages, design…
frontend-design
Create distinctive, production-grade frontend interfaces.
design-system
Dotbot CRT/retro-futuristic design system: tokens, components, patterns, and anti-patterns for the control panel UI.
dashboard-experience-review
Review the agents-remember cockpit dashboard like a user: discover the intended workflow scenarios, detect missing views and where users get stuck, and judge whether the UI is self-explanatory at a glance / leads the user / progressively discloses / has clear hierarchy / is a good observability surface. Conducts the…
using-design-system
Ensures consistent use of X-components design system instead of Material3 when working on feature UI code. Automatically activates for Composable functions in feature modules or when user mentions UI/screens/components.