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/josstei/maestro-orchestrate/design_system_engineergit clone --depth 1 https://github.com/josstei/maestro-orchestrateWrote 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/josstei/maestro-orchestrate/design_system_engineer)<a href="https://agentmods.dev/agents/josstei/maestro-orchestrate/design_system_engineer"><img src="https://agentmods.dev/badge/agents/josstei/maestro-orchestrate/design_system_engineer.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.00088 | $0.00211 |
| Opus 5 | $0.00044 | $0.00105 |
| Sonnet 5 | $0.00018 | $0.00042 |
| Haiku 4.5 | $0.00009 | $0.00021 |
Grade A, and why
design_system_engineer 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
Agent methodology loaded via MCP tool get_agent. Call get_agent(agents: ["design-system-engineer"]) to read the full methodology at delegation time.
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 · 23 lines · 88 tokens per session scan A d11e39160a26
design_system_engineer is an agent published in the GitHub repository josstei/maestro-orchestrate (460 stars, last pushed 27d ago), licensed Apache-2.0. It adds 88 tokens to every session and 211 once invoked, about $0.0004 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
ui-ux-designer
🎨 UI/UX 设计师 - 为前端功能生成页面结构、组件拆分和交互流程设计.
hatch3r-reviewer
Expert code reviewer for the project. Proactively reviews code for quality, security, privacy invariants, performance, accessibility, and adherence to specs.
ui-design-agent
UI design token management and prototype generation — W3C Design Tokens Format, state-based components, WCAG AA validation, responsive layout templates.
form
FORM — Design. Visual system, UI architecture, motion, accessibility, design PRDs. Use when a human will see the work, when a landing page or product UI is requested, or when Forge is about to invent a look. Use proactively for any user-facing surface.
ui-designer
Design user interface and experience.
designer
UI/UX Designer-Developer for user-facing surfaces — implements to the Expressive baseline (taste-skill-v2, always) plus the Functional functional-ui density overlay when the conductor names it, and dial values. Used only on UI/UX jobs; never self-approves.