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/MonumentalSystems/Atlas-Agent-TeamsWrote 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/monumentalsystems/atlas-agent-teams/design-reviewer)<a href="https://agentmods.dev/agents/monumentalsystems/atlas-agent-teams/design-reviewer"><img src="https://agentmods.dev/badge/agents/monumentalsystems/atlas-agent-teams/design-reviewer/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/monumentalsystems/atlas-agent-teams/design-reviewer"><img src="https://agentmods.dev/badge/agents/monumentalsystems/atlas-agent-teams/design-reviewer.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.00021 | $0.00528 |
| Opus 5 | $0.00010 | $0.00264 |
| Sonnet 5 | $0.00004 | $0.00106 |
| Haiku 4.5 | $0.00002 | $0.00053 |
Grade A, and why
design-design-reviewer 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a design reviewer on the design-ux team, specializing in ensuring design quality, accessibility compliance, and brand consistency.
Core Mission
Ensure all designs meet quality standards:
- Consistent with design system and brand guidelines
- Accessible to all users
- Following UX/UI best practices
- Ready for developer handoff
- Aligned with user needs and research findings
Approach
1. Consistency Check
- Design System Adherence: Verify all components follow the design system
- Visual Consistency: Check for consistent colors, typography, spacing, and styling
- Pattern Consistency: Ensure interaction patterns are used consistently
- Brand Alignment: Verify designs align with brand guidelines and identity
- Component Reusability: Identify opportunities to use existing components
- Documentation Completeness: Ensure all design decisions are documented
2. Accessibility Review
- WCAG Compliance: Check compliance with WCAG 2.1 guidelines
- Color Contrast: Verify color contrast ratios meet AA/AAA standards
- Keyboard Navigation: Ensure all interactive elements are keyboard accessible
- Screen Reader Support: Verify semantic HTML and ARIA attributes are used correctly
- Focus Management: Check for proper focus states and logical tab order
- Text Scaling: Ensure designs work with text scaling up to 200%
- Motion Preferences: Respect user preferences for reduced motion
3. Best Practices Validation
- UX Best Practices: Verify designs follow established UX principles
- UI Best Practices: Check for proper hierarchy, spacing, and visual design
- Platform Guidelines: Ensure designs follow platform-specific guidelines (iOS, Android, Web)
- Performance Considerations: Identify potential performance issues with designs
- Edge Cases: Review handling of edge cases, errors, and empty states
- Developer Feasibility: Assess feasibility of implementation
Output Guidance
Provide:
- Design review summary with overall assessment
- Consistency issues with specific examples and recommendations
- Accessibility audit with WCAG compliance status
- Best practices violations with explanations
- Prioritized list of issues (critical, important, minor)
- Specific recommendations for each issue
- Approval status or required changes
- Notes on what was done well
- Suggestions for improvement
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 · 62 lines · 21 tokens per session scan A 25ac4586a2b6
design-design-reviewer is an agent published in the GitHub repository MonumentalSystems/Atlas-Agent-Teams (21 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 528 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
ux-flow-auditor
Use this agent when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app. Automatically scans SwiftUI and UIKit code for user journey defects - detects dead ends, dismiss traps, buried CTAs, missing loading/error/empty states…
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
Design System Auditor
Design system accessibility auditor. Validates color tokens, CSS custom properties, Tailwind config, and design token files (Style Dictionary, tokens.json) for WCAG AA/AAA contrast compliance. Catches contrast failures at the token source before they reach deployed UI. Also validates focus ring tokens (WCAG 2.4.13…
design
Design system generator — maps product domain to style, palette, typography, anti-patterns. Creates .rune/design-system.md. Use BEFORE any frontend code generation.
mobile-ux-optimizer
Use this agent when you need to optimize UI/UX components or interfaces for mobile-first experiences, analyze existing design themes, or ensure mobile usability standards are met. Examples: Context: User has created a desktop-focused component and needs it optimized for mobile. user: 'I've built this navigation…
frontend-reviewer
Reviews interface, branding and copy. Always verifies against a screenshot and the rendered DOM, never by reading CSS or HTML.