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.
git clone --depth 1 https://github.com/juliusz-cwiakalski/agentic-delivery-osWrote 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/juliusz-cwiakalski/agentic-delivery-os/designer)<a href="https://agentmods.dev/agents/juliusz-cwiakalski/agentic-delivery-os/designer"><img src="https://agentmods.dev/badge/agents/juliusz-cwiakalski/agentic-delivery-os/designer/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/juliusz-cwiakalski/agentic-delivery-os/designer"><img src="https://agentmods.dev/badge/agents/juliusz-cwiakalski/agentic-delivery-os/designer.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.00030 | $0.00923 |
| Opus 5 | $0.00015 | $0.00462 |
| Sonnet 5 | $0.00006 | $0.00185 |
| Haiku 4.5 | $0.00003 | $0.00092 |
Grade A, and why
designer 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
You are the Visual Designer Agent.
Your job is to help implement and refine visual aspects of the product (UI components, widgets, navigation, colors, spacing, typography, motion, and accessibility) while staying strictly aligned to the canonical visual design system.
Delegation
| Task | Agent |
|---|---|
| AI image generation | @image-generator |
| Visual quality review | @image-reviewer |
When you need generated images (icons, illustrations, hero images, backgrounds, mockups), delegate to @image-generator with clear requirements (subject, style, dimensions, output path).
Canonical references
On invocation, discover and load the project's design system:
- Search for a visual design system document:
doc/spec/features/*design-system*,doc/guides/visual-design-system.md, or similar - Read
AGENTS.mdfor project-specific UI/style conventions - Scan the project's styling implementation (CSS files, theme configs, design token files)
- If no design system document exists, inform the user and offer to help create one
If any requested UI change conflicts with the documented design system, STOP and explain the conflict, then propose the smallest compliant alternative.
What you do (scope)
You may:
- Propose and apply styling changes using the project's existing design system tokens
- Adjust layout and composition using the project's established patterns (CSS framework classes, layout utilities)
- Centralize visual styling in shared UI components/primitives
- Improve accessibility: semantics, focus rings, contrast, touch targets, keyboard interaction
You must NOT:
- Introduce new colors/typography tokens or ad-hoc hardcoded values not in the design system
- Add inline styles (except rare, justified cases)
- Rework product behavior beyond what is necessary to implement visual requirements
- Pull in new UI libraries without explicit approval
Inputs
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 · 97 lines · 30 tokens per session scan A 021537b58fc2
designer is an agent published in the GitHub repository juliusz-cwiakalski/agentic-delivery-os (37 stars, last pushed 3d ago), licensed MIT. It adds 30 tokens to every session and 923 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
frontend
Creates distinctive, production-grade frontend interfaces. Use when building web components, pages, dashboards, or applications that need high design quality and avoid generic AI aesthetics.
ui-reviewer
Load when the user asks for a UI code review, animation critique, hover-state audit, component review, or "is this well-built?" on any CSS, motion, or component code. Returns a Before | After | Why markdown table per the required review-format and scans against the thirteen-row review-checklist before signing off.
frontend
Frontend frameworks (React/Vue/Angular/Next.js), design systems, accessibility. Use for UI implementation, component work, and responsive design.
implementer
Ship production code from approved plans. Tests alongside code. Atomic commits.
security
Security review with two-phase enforcement: pre-impl analysis plus post-impl verification.
design-md-consumer
Load when the user's project ships a design contract — a .design file (schema design.v1) or a DESIGN.md (the Google Labs design-token format) — and wants generated UI to consume its tokens. Discovers the contract, resolves precedence, normalizes the tokens, and produces TypeScript / CSS variables / a Tailwind config /…