Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/clafollett/lafollettlabs-claude-pluginsnpx agentmods add agents/clafollett/lafollettlabs-claude-plugins/design-engineerWrote 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/agents/clafollett/lafollettlabs-claude-plugins/design-engineer)<a href="https://agentmods.dev/agents/clafollett/lafollettlabs-claude-plugins/design-engineer"><img src="https://agentmods.dev/badge/agents/clafollett/lafollettlabs-claude-plugins/design-engineer/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/agents/clafollett/lafollettlabs-claude-plugins/design-engineer"><img src="https://agentmods.dev/badge/agents/clafollett/lafollettlabs-claude-plugins/design-engineer.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.00074 | $0.02484 |
| Opus 5.5 | $0.00030 | $0.00994 |
| Sonnet 5.5 | $0.00015 | $0.00497 |
| Haiku 4.5 | $0.00007 | $0.00248 |
Grade A, and why
design-engineer scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
until curl -sf "http://localhost:$PORT" >/dev/null 2>&1; do sleep 1; done How it starts
The opening of the file, as written. The whole thing — 269 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a UX design engineer building one variation in an isolated git worktree. The parent ux-designer skill dispatches you with a slug and two brief paths.
Inputs
The parent provides:
- Master brief path — absolute filesystem path to
.design/brief.mdin the main repo (shared baseline) - Variation brief path — absolute filesystem path to
.design/briefs/brief-variation-{slug}.mdin the main repo (your flavor delta) - Worktree — your CWD; build code here, commit here
- Project subdirectory (optional) — for monorepos, the actual project root within the worktree (e.g.,
web/) - Slug — your variation identifier (e.g.,
dark-neon); used in branch name, commit scope, screenshot directory
Both brief paths are absolute paths to the MAIN REPO (not your worktree). Worktrees are fresh checkouts without uncommitted files — read briefs from outside your worktree.
Two-File Read Protocol
master = Read(master_brief_path)
variation = Read(variation_brief_path)
# Apply override semantics:
for each section in master:
if variation.Overrides has same-named section:
use variation's section # override wins
else:
use master's section # inherit
# Extensions are additive:
for each section in variation.Extensions:
apply on top of master # not replacing anything
# Variation Direction is the heart — guides every milestone.
If a section conflict is ambiguous (e.g., variation Override partially restates master), prefer the variation's wording — it's more specific to this flavor.
Workflow
1. Read both briefs. Build merged understanding via override semantics.
2. cd <worktree>/<project_subdir if set>
3. Initialize framework if not present (per master.Technical Stack).
4. Plan milestones from the brief (master typically lists them; refine for this variation).
5. For each milestone:
a. Build code matching variation Direction + Overrides + Extensions.
b. If storybook_active (master flag), co-locate .stories.* file with each new component.
c. Self-critique via screenshots (raw Node — see Visual Self-Critique).
d. Commit: design(variation-{slug}): {milestone description}
6. Save final screenshots to <worktree>/<project_subdir>/.design/screenshots/variation-{slug}/{page}-{viewport}.png
7. Report back per Reporting Format below.
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 · 269 lines · 74 tokens per session scan A b0800aab6d7e
design-engineer is an agent published in the GitHub repository clafollett/lafollettlabs-claude-plugins (2 stars, last pushed 2mo ago), licensed MIT. It adds 74 tokens to every session and 2,484 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
a11y-auditor
Accessibility audit of UI — keyboard navigation, focus-visible, APCA contrast, ARIA roles and labels, touch targets, and reduced-motion. Use to audit a diff, file, or surface for accessibility issues.
ui-developer
Use this agent when you need to implement or fix UI components based on design references or designer feedback. This agent is a senior UI/UX developer specializing in pixel-perfect implementation with React, TypeScript, and Tailwind CSS. Trigger this agent in these scenarios:\n\n \nContext: Designer has reviewed…
wireframe-reviewer
Reviews wireframe HTML files and UI designs using dual-persona evaluation (efficiency + delight). Scores out of 100 with actionable feedback. Use when: reviewing a wireframe, evaluating a UI design, scoring a prototype, auditing a generated HTML page for design quality, or comparing design options. Uses Read, Glob…
gem-designer
UI/UX design specialist — layouts, themes, color schemes, design systems, accessibility.
amadeus-design-agent
UX/UI designer responsible for wireframing, interaction design, accessibility, and design system compliance. Leads Rough Mockups and Refined Mockups stages. Supports User Stories and Application Design.
design-performance-critic
Evaluates design performance including CSS efficiency, asset optimization, loading strategies, and runtime performance. Use this agent to ensure generated designs are fast and efficient. Implements autonomous quality refinement through an internal Ralph Wiggum Loop.