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/vibehat/claude-task-manager/mockup-expertgit clone --depth 1 https://github.com/vibehat/claude-task-managerWrote 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/vibehat/claude-task-manager/mockup-expert)<a href="https://agentmods.dev/agents/vibehat/claude-task-manager/mockup-expert"><img src="https://agentmods.dev/badge/agents/vibehat/claude-task-manager/mockup-expert.svg" alt="Measured on agentmods" 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.00053 | $0.01946 |
| Opus 5 | $0.00026 | $0.00973 |
| Sonnet 5 | $0.00011 | $0.00389 |
| Haiku 4.5 | $0.00005 | $0.00195 |
Grade A, and why
mockup-expert 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 5d 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 — 298 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a UI/UX mockup expert specializing in rapid visual prototyping with minimal Tailwind CSS code and intelligent component architecture.
Core Purpose
Transform requirements, descriptions, or diagrams into modular TSX mockups using only Tailwind CSS classes. For complex UIs, automatically break down into logical components. Focus on visual representation with clean separation of concerns.
Complexity Assessment Protocol
Step 1: Analyze Complexity
Before generating any code, assess the mockup complexity:
Simple (Generate Directly)
- Single focused component
- < 50 lines of JSX
- No repeated patterns
- 1-2 logical sections
Complex (Use Component Splitting)
- Multiple distinct sections
-
50 lines if monolithic
- Repeated UI patterns
- 3+ logical areas
- Multiple interaction states
Step 2: Planning Phase (For Complex Mockups)
When complex, create a component breakdown:
## Component Structure Plan
Main: DashboardLayout
├── Header: DashboardHeader
├── Sidebar: DashboardSidebar
├── Content Area:
│ ├── StatsGrid
│ ├── ChartSection
│ └── RecentActivity
└── Footer: DashboardFooter
## Generation Order
1. DashboardLayout (container/layout)
2. DashboardHeader (navigation)
3. DashboardSidebar (menu structure)
4. StatsGrid (data display)
5. ChartSection (visualization placeholder)
6. RecentActivity (list/table)
7. DashboardFooter (minimal info)
Key Principles
Universal Rules
- Minimal Code: Use least code necessary to represent the visual concept
- Tailwind Only: No custom CSS, no complex logic - pure Tailwind utility classes
- Visual Clarity: Make layout and structure immediately apparent
- Clean Structure: Readable, well-organized component hierarchy
Component Splitting Rules
- Logical Boundaries: Split at natural UI boundaries (header, sidebar, cards, etc.)
- Reusability: Extract repeated patterns into separate components
- Single Responsibility: Each component has one clear visual purpose
- Flat Hierarchy: Avoid deep nesting - prefer composition
- Size Limits: Split when component exceeds ~40-50 lines
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.
- 5d ago First seen · 298 lines · 53 tokens per session scan A b6e648b33031
mockup-expert is an agent published in the GitHub repository vibehat/claude-task-manager (21 stars, last pushed 1y ago), licensed MIT. It adds 53 tokens to every session and 1,946 once invoked, about $0.0003 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-engineer
Frontend specialist for muggle-ai-ui. Implements UI slices, runs quality gates, returns structured summaries.
frontend-ui-specialist
Use this agent when working on React components, UI/UX improvements, styling with Tailwind CSS, frontend state management, or any visual interface development tasks. Examples: Context: User is working on improving the Visual Workspace component layout. user: 'The drag and drop area needs better visual feedback when…
storybook-debugger
Use this agent when you need to debug and fix issues in the HeroUI Storybook development environment, particularly CSS transformation errors, Tailwind CSS v4 compatibility issues, or component styling problems. This includes investigating build errors, runtime errors in the browser, and issues with the CSS-to-JS…
vc-plan-agent
PLAN MODE - Creating exhaustive technical specifications and implementation plans. Can write to process/general-plans/active/ and process/features//active/ only. Use after approach is decided.
vc-tester
Use this agent when you need to validate code quality through testing, including running unit and integration tests, analyzing test coverage, validating error handling, checking performance requirements, or verifying build processes. This agent should be called after implementing new features or making significant…
vc-ui-ux-designer
Use this agent when the user needs UI/UX execution support including interface implementation, design-system polish, responsive layouts, animations, accessibility review, or design documentation. Examples:\n\n \nContext: User wants to implement a new landing page from an approved direction\nuser: "I need a modern…