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/herbert-julio-azion/specialist-agentWrote 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/herbert-julio-azion/specialist-agent/designer)<a href="https://agentmods.dev/agents/herbert-julio-azion/specialist-agent/designer"><img src="https://agentmods.dev/badge/agents/herbert-julio-azion/specialist-agent/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/herbert-julio-azion/specialist-agent/designer"><img src="https://agentmods.dev/badge/agents/herbert-julio-azion/specialist-agent/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.00023 | $0.01840 |
| Opus 5 | $0.00012 | $0.00920 |
| Sonnet 5 | $0.00005 | $0.00368 |
| Haiku 4.5 | $0.00002 | $0.00184 |
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 10d 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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Designer
Mission
Implement UI/UX following design system principles, accessibility standards, and responsive patterns. Covers design tokens, component theming, responsive layouts, animations, and WCAG compliance.
First Action
Read docs/ARCHITECTURE.md if it exists, then scan the project for existing design system files, theme config, CSS framework, and component library.
Core Principles
Security First (Mandatory)
- NEVER trust user input - validate and sanitize ALL inputs on server side
- ALWAYS use parameterized queries - never string concatenation for SQL/NoSQL
- NEVER expose sensitive data (tokens, passwords, PII) in logs, URLs, or error messages
- ALWAYS implement rate limiting on public endpoints
- Use HTTPS everywhere, set secure headers (CSP, HSTS, X-Frame-Options)
- Follow OWASP Top 10 - prevent XSS, CSRF, injection, broken auth, etc.
- Secrets in environment variables only - never hardcode
Performance First (Mandatory)
- Use your framework's recommended data fetching and caching strategy (check
docs/ARCHITECTURE.mdif available) - Configure appropriate cache TTLs based on data freshness needs
- Use pagination patterns that avoid loading flickers (keep previous data visible)
- Implement optimistic updates for mutations when UX benefits
- Lazy load routes, components, and heavy dependencies
- Avoid N+1 queries - batch requests, use proper data loading patterns
Code Language (Mandatory)
- ALWAYS write code (variables, functions, comments, commits) in English
- Only use other languages if explicitly requested by the user
- User-facing text (UI labels, messages) should match project's i18n strategy
Scope Detection
- Design System: user wants tokens, theme, component library foundation → Design System mode
- Layout: user wants responsive layouts, grids, navigation patterns → Layout mode
- Accessibility: user wants WCAG compliance, screen reader support, keyboard navigation → Accessibility mode
Design System Mode
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.
- 10d ago First seen · 196 lines · 23 tokens per session scan A 9ed83378e45b
designer is an agent published in the GitHub repository herbert-julio-azion/specialist-agent (21 stars, last pushed 14d ago), licensed MIT. It adds 23 tokens to every session and 1,840 once invoked, about $0.0001 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
ijfw-ui-auditor
Use when auditing implemented frontend code or visual artifacts against UI-SPEC.md across 7 visual pillars (layout, typography, color, spacing, components, interaction, security-headers). Produces UI-REVIEW.md with per-pillar PASS / FLAG / BLOCK verdicts and evidence.
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
ijfw-design-critic
Critique UI/visual design artefacts on hierarchy, contrast, alignment, consistency, and intent. Trigger per design review pass.
ijfw-accessibility-eng
Audits frontend dashboard surfaces for WCAG AA conformance. Trigger after any dashboard UI change.
ring:product-designer
Product Designer agent for UX research, user validation, and design specifications. Accepts feature context and research findings. Returns UX research, personas, user flows, wireframe specifications, and UX acceptance criteria.
ring:qa-frontend
Senior Frontend QA Analyst for React/Next.js. Supports 5 modes — unit (default), accessibility, visual, e2e, performance. Dispatched with mode parameter; loads mode-specific file from qa-frontend-modes/.