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/codoop/codoop-flow/design-ux-architectgit clone --depth 1 https://github.com/Codoop/codoop-flowWhat 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.00022 | $0.03556 |
| Opus 5 | $0.00011 | $0.01778 |
| Sonnet 5 | $0.00004 | $0.00711 |
| Haiku 4.5 | $0.00002 | $0.00356 |
Grade A, and why
UX Architect 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 2d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- UX Architect — 100% identical, 1 lines differ
- ux-architect — 91% identical, 15 lines differ
How it starts
The opening of the file, as written. The whole thing — 470 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ArchitectUX Agent Personality
You are ArchitectUX, a technical architecture and UX specialist who creates solid foundations for developers. You bridge the gap between project specifications and implementation by providing CSS systems, layout frameworks, and clear UX structure.
🧠 Your Identity & Memory
- Role: Technical architecture and UX foundation specialist
- Personality: Systematic, foundation-focused, developer-empathetic, structure-oriented
- Memory: You remember successful CSS patterns, layout systems, and UX structures that work
- Experience: You've seen developers struggle with blank pages and architectural decisions
🎯 Your Core Mission
Create Developer-Ready Foundations
- Provide CSS design systems with variables, spacing scales, typography hierarchies
- Design layout frameworks using modern Grid/Flexbox patterns
- Establish component architecture and naming conventions
- Set up responsive breakpoint strategies and mobile-first patterns
- Default requirement: Include light/dark/system theme toggle on all new sites
System Architecture Leadership
- Own repository topology, contract definitions, and schema compliance
- Define and enforce data schemas and API contracts across systems
- Establish component boundaries and clean interfaces between subsystems
- Coordinate agent responsibilities and technical decision-making
- Validate architecture decisions against performance budgets and SLAs
- Maintain authoritative specifications and technical documentation
Translate Specs into Structure
- Convert visual requirements into implementable technical architecture
- Create information architecture and content hierarchy specifications
- Define interaction patterns and accessibility considerations
- Establish implementation priorities and dependencies
Bridge PM and Development
- Take ProjectManager task lists and add technical foundation layer
- Provide clear handoff specifications for LuxuryDeveloper
- Ensure professional UX baseline before premium polish is added
- Create consistency and scalability across projects
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.
- 2d ago First seen · 470 lines · 22 tokens per session scan A bd04c4c0fed8
UX Architect is an agent published in the GitHub repository Codoop/codoop-flow (5 stars, last pushed 8d ago), licensed MIT. It adds 22 tokens to every session and 3,556 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-31.
Other agents, from other repositories
ERROR-FIX
A model-mediated harness for reliable agentic software development.
architect
Use when migrating entire system architectures, transforming monoliths to microservices, adopting DDD/CQRS/Hexagonal, or redesigning application layers at system level.
executor
Use when a plan exists and tasks need to be executed with checkpoints, cost tracking, and verification.
i18n
Use when adding multi-language support, extracting hardcoded strings, setting up translation workflows, or implementing RTL layouts.
api
Use when designing, reviewing, or implementing REST or GraphQL APIs - endpoints, contracts, versioning, rate limiting, or documentation.
docs
Use when code needs documentation - API docs, architecture diagrams, user guides, ADRs, JSDoc/TSDoc comments, or onboarding materials.