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 Dragoon0x/everything-design-taste --skill design-org-structuregit clone --depth 1 https://github.com/Dragoon0x/everything-design-tasteWrote 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/dragoon0x/everything-design-taste/design-org-structure)<a href="https://agentmods.dev/skills/dragoon0x/everything-design-taste/design-org-structure"><img src="https://agentmods.dev/badge/skills/dragoon0x/everything-design-taste/design-org-structure/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/dragoon0x/everything-design-taste/design-org-structure"><img src="https://agentmods.dev/badge/skills/dragoon0x/everything-design-taste/design-org-structure.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.00025 | $0.00626 |
| Opus 5.5 | $0.00010 | $0.00250 |
| Sonnet 5.5 | $0.00005 | $0.00125 |
| Haiku 4.5 | $0.00003 | $0.00063 |
Grade A, and why
design-org-structure 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 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.
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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Org Structure
Team Models
Centralized
All designers report to a design lead. They're assigned to product teams but their career and craft development lives in the design org.
Pros: Consistent quality, strong design culture, clear career paths Cons: Potential disconnect from product teams, resource allocation friction Best for: Companies where design consistency matters more than speed
Embedded
Each designer reports directly to a product team lead. No central design org.
Pros: Fast, tight product alignment, designers have full context Cons: Quality drift, isolation, no design mentorship, career path unclear Best for: Early-stage startups where speed is everything
Hybrid (most common at scale)
Designers are embedded in product teams but have a dotted line to a central design leader. Regular design org rituals (critique, design system work) keep quality aligned.
Pros: Speed of embedded + quality of centralized Cons: Complex management, potential conflicting priorities Best for: Growth-stage companies (50-500 employees)
Designer-to-Engineer Ratio
Benchmarks
- Early startup: 1 designer per 8-10 engineers
- Growth stage: 1 designer per 5-7 engineers
- Mature product: 1 designer per 3-5 engineers
- Design-led products: 1 designer per 2-3 engineers
When to Hire
- Designers are consistently the bottleneck
- Quality is dropping because designers are spread too thin
- You're entering a new market/product area
- Design debt is accumulating faster than you can address it
Roles and Levels
IC Track
- Junior Designer — Executes defined tasks, learning the craft
- Designer — Owns features end-to-end, works independently
- Senior Designer — Drives strategy for product areas, mentors juniors
- Staff Designer — Cross-product impact, defines systems and standards
- Principal Designer — Company-wide influence, sets design direction
Management Track
- Design Lead — Player-coach, manages 3-5 designers
- Design Manager — Full-time people management, 5-8 reports
- Director of Design — Org strategy, cross-functional leadership
- VP of Design — Executive team, company strategy, org building
- CDO/Head of Design — Board-level, brand and product vision
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 · 69 lines · 25 tokens per session scan A ed95274fbcf6
design-org-structure is a skill published in the GitHub repository Dragoon0x/everything-design-taste (13 stars, last pushed 6mo ago), licensed MIT. It adds 25 tokens to every session and 626 once invoked, about $0.0001 per session on Opus 5.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-09-03.
Other skills, from other repositories
antislop
Anti Slop: Rules for AI Coding Agents. The core filter. Load always to stop generic AI slop.
antislop-human
Human and accessibility skill for antislop. Contrast, keyboard, focus, and states for real people. Includes the contrast checker.
antislop-ui
UI and visual skill for antislop. Use when building or editing any interface: color, layout, components, motion. Load with the core.
role-ui-ux-designer
Use when orchestrating UI/UX design systems, anti-AI-slop frontend styling, tactile micro-interactions, responsive design tokens, accessibility standards, and high-fidelity interface engineering.
taste
Anti-slop frontend engineering directive and design taste system. Enforces brief inference, dynamic design dials, absolute prohibition of AI visual tells, and 100% full-output completion.
design-taste-frontend
A page built by a model usually looks like the average of every page the model has seen: a centred headline over three lines, a little label above it, a row of icon cards, a soft gradient, a few thin rules and a monospace caption. Nothing in it is wrong and nothing in it was decided.