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 liqiongyu/lenny_skills_plus --skill design-engineeringgit clone --depth 1 https://github.com/liqiongyu/lenny_skills_plusWrote 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/liqiongyu/lenny_skills_plus/design-engineering)<a href="https://agentmods.dev/skills/liqiongyu/lenny_skills_plus/design-engineering"><img src="https://agentmods.dev/badge/skills/liqiongyu/lenny_skills_plus/design-engineering/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/liqiongyu/lenny_skills_plus/design-engineering"><img src="https://agentmods.dev/badge/skills/liqiongyu/lenny_skills_plus/design-engineering.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.02065 |
| Opus 5 | $0.00011 | $0.01033 |
| Sonnet 5 | $0.00004 | $0.00413 |
| Haiku 4.5 | $0.00002 | $0.00206 |
Grade A, and why
design-engineering 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 11d 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Engineering
Scope
Covers
- Defining a Design Engineering function (hybrid design sensibility + ability to ship production code)
- Choosing an operating model: embedded vs platform/design-system vs tiger team
- Creating a prototype → production pipeline (what is throwaway vs shippable)
- Establishing a design-to-code contract (tokens, components, reviews, quality bar)
- Planning delivery for UI/UX-heavy work (components/flows, milestones, QA gates)
When to use
- “We want to create a design engineering function—write the charter and operating model.”
- “Our prototypes never make it to production—define a prototype→production workflow.”
- “We need faster UI iteration with high craft—set a design-to-code contract + quality bar.”
- “We’re building a new UI/component library—create a component delivery plan and reviews.”
When NOT to use
- You need UX research, discovery, or product strategy (use interviews/surveys/PRD skills).
- You’re doing mostly backend/platform architecture with minimal UI surface area.
- You only need to ship a single small UI fix (just implement it).
- You need a brand/visual identity system (separate design/brand process).
- You want to build or evolve a design system (tokens, components, governance) without standing up a new practice (use
design-systems). - You want to improve engineering team culture, rituals, or hiring practices (use
engineering-culture). - You need to run a one-off design review or design critique session (use
running-design-reviews). - You need a feature spec or detailed UX flow document (use
writing-specs-designs).
Inputs
Minimum required
- Product/context: what you’re building and who it’s for
- Current state: design artifacts (Figma, mockups) + codebase/stack (web/native) + existing design system (if any)
- Goal: what “better” means (speed, consistency, craft, accessibility, quality, fewer handoff bugs)
- Constraints: team composition, timeline, quality bar, accessibility/compliance requirements
What ships with it
13 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.
- eval/eval_config.json 879 B
- eval/SHOWCASE.md 5.2 KB
- eval/with_skill.md 38 KB
- eval/without_skill.md 18 KB
- README.md 1.7 KB
- references/CHECKLISTS.md 1.9 KB
- references/EXAMPLES.md 1.6 KB
- references/INTAKE.md 1.2 KB
- references/RUBRIC.md 4.3 KB
- references/SOURCE_SUMMARY.md 984 B
- references/TEMPLATES.md 2.8 KB
- references/WORKFLOW.md 3.6 KB
- skillpack.json 371 B
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.
- 11d ago First seen · 129 lines · 22 tokens per session scan A 582000dfc43a
design-engineering is a skill published in the GitHub repository liqiongyu/lenny_skills_plus (52 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 22 tokens to every session and 2,065 once invoked, about $0.0001 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
plan
Use when a request needs shaping before any code is written — a rough or vague prompt to sharpen, an ambiguous idea to design, or a clear-enough task to decompose. One chain-starter that amplifies the prompt, designs the approach, and decomposes it into a batched task file, skipping whichever phases the request…
decision-heuristics
A set of heuristics for making difficult personal decisions such as changing jobs, buying a home, moving, forming a partnership, or getting married. It is intended for major choices, not everyday decisions.
screen-detox
A habit-change framework for reducing non-work screen use such as social media, short videos, games, and endless scrolling.
happiness-skill
A Chinese-language guide to happiness based on reducing unmet wants, focusing on the present, and treating happiness as a trainable skill.
monkey-mind-meditation
A meditation and reflection guide for a busy or anxious mind. It treats recurring thoughts as something to observe and examine, while noting that acute serious mental-health problems need professional care.
peer-selection
A guide for thinking about which friends, partners, and social circles to keep close, based on shared values and their influence on your life.