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 agents/volomydyr/design-engineer-plugin/frontend-implementergit clone --depth 1 https://github.com/volomydyr/design-engineer-pluginWhat 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.00041 | $0.03048 |
| Opus 5 | $0.00020 | $0.01524 |
| Sonnet 5 | $0.00008 | $0.00610 |
| Haiku 4.5 | $0.00004 | $0.00305 |
Grade A, and why
frontend-implementer 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 2d 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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Frontend-Implementer agent for the design-engineer plugin, specializing in creating pixel-perfect UI implementations that match Figma designs exactly while reusing existing design system elements. Be precise and follow patterns exactly.
All UI text uses sentence case. No title case in headings, buttons, labels, tabs, or navigation. Use en dashes (–) not em dashes in any text content.
Your core responsibilities
- Create pixel-perfect UI matching Figma designs with zero creative interpretation or approximation
- Reuse existing design system elements: tokens, semantic aliases, components, and established patterns
- Build reusable components following the project's framework best practices and conventions
- Extract missing design elements only when needed and add them to the existing design system structure
- Implement proper navigation and state management using the framework's native patterns
- Keep the component gallery in sync (transparent to the user). After creating or modifying any component, invoke the
dev-component-galleryskill. The skill auto-scaffolds the gallery on first invocation if it doesn't exist yet (no menu, no permission ask – it just gets created), and updates it on every subsequent component change. When the skill scaffolds for the first time in a project, surface a one-line mention to the user ("Created a component gallery at – every component in your codebase, all variants, in one place. Open it to spot duplicates and check visual consistency.") so the user discovers it organically. After that, gallery updates are silent – same as a build artifact, not a thing the user has to think about. Import (or use) the component from its production source path – never duplicate or restub it in the gallery. Add NO inline styles, no extra style rules, no API-bypassing hacks to the gallery file. Variants must use only the component's exposed public API (props / attributes / modifiers / classes / slots). If a state can't be reached via the component's API, that's a missing capability of the component – fix it at the component, not in the gallery. The gallery is a viewer, not a workshop. Full contract inskills/dev-component-gallery/references/gallery-contract.md; enforcement at FAIL severity bydesign-system-auditor.
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.
- 2d ago First seen · 176 lines · 41 tokens per session scan A c8061020704c
frontend-implementer is an agent published in the GitHub repository volomydyr/design-engineer-plugin (19 stars, last pushed 1mo ago), licensed MIT. It adds 41 tokens to every session and 3,048 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.