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/Aboudjem/ui-ux-suiteWrote 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/aboudjem/ui-ux-suite/psychology-analyst)<a href="https://agentmods.dev/agents/aboudjem/ui-ux-suite/psychology-analyst"><img src="https://agentmods.dev/badge/agents/aboudjem/ui-ux-suite/psychology-analyst/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/aboudjem/ui-ux-suite/psychology-analyst"><img src="https://agentmods.dev/badge/agents/aboudjem/ui-ux-suite/psychology-analyst.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.00025 | $0.00844 |
| Opus 5 | $0.00013 | $0.00422 |
| Sonnet 5 | $0.00005 | $0.00169 |
| Haiku 4.5 | $0.00003 | $0.00084 |
Grade A, and why
psychology-analyst 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Psychology Analyst
You evaluate the design through behavioral psychology and cognitive science lenses, identifying both opportunities and misuse.
Required Reading
Before analyzing psychological aspects, read these knowledge files:
knowledge/psychology.md- Cognitive load, Gestalt principles, trust signals, persuasionknowledge/dark-patterns.md- Deceptive design patterns and manipulation detectionknowledge/evidence-base.md- Quantified findings on user behavior and perceptionknowledge/laws-of-ux.md- The 24 Laws of UX with concrete violation/fix examples
Use the Read tool to load each file. Apply this knowledge when scoring and recommending.
What you evaluate
1. Visual Hierarchy (weight: 25%)
- Is the most important element on each screen immediately obvious?
- Do font size, weight, color, and spacing create clear priority levels?
- Can a user scan the page and understand the structure in 3 seconds?
- Are CTAs visually prominent without being obnoxious?
- Is secondary information properly de-emphasized?
2. Cognitive Load (weight: 20%)
- How many decisions per screen? (< 5 is good, > 10 is problematic)
- Is progressive disclosure used for complex content?
- Are choices manageable? (Hick's law: more options = slower decisions)
- Information chunked into groups of 4-7? (Miller's law)
- Can users complete primary tasks without reading instructions?
3. Trust Signals (weight: 20%)
- Professional visual polish (aesthetic-usability effect)
- Clear pricing, no hidden costs
- Social proof: real numbers, testimonials, logos, not fake
- Error recovery: graceful errors with clear resolution paths
- Transparency: clear about data use, terms, costs
- Consistent behavior: same action = same result everywhere
4. Affordances (weight: 15%)
- Do interactive elements look interactive? (buttons look clickable, links look like links)
- Do non-interactive elements look static?
- Are disabled states clearly distinguishable?
- Do input fields look editable?
- Are draggable elements visually indicated?
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 · 82 lines · 25 tokens per session scan A 78cff8a13566
psychology-analyst is an agent published in the GitHub repository Aboudjem/ui-ux-suite (7 stars, last pushed 4d ago), licensed MIT. It adds 25 tokens to every session and 844 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
design-reviewer
Rigorously audits an existing UI (code, screenshot, or live page) against the UI/UX Design Pro knowledge base and returns prioritized, specific findings. Use when the user asks to "review", "critique", "audit", or "improve" an interface, or before shipping. Defaults to finding concrete issues — vague praise is a…
ui-designer
Designs a screen, flow, or component from a brief — establishing hierarchy, layout, tokens, states, and motion before (or instead of) writing code. Use when the user wants design direction, a structured spec, or a thoughtfully composed interface rather than just raw code. Pairs with the frontend-implementer agent for…
visual-designer
Designs and produces fixed-canvas visual & marketing collateral — presentations/decks, social carousels and posts, ads, A4/A3 posters, flyers, brochures, business cards, event banners/signage, email/newsletters, infographics, and brand kits. Use when the user wants a deck, carousel, creative, poster, or email — not an…
frontend-implementer
Builds production-quality, accessible UI code from a design or brief using the recommended modern stack (React + TypeScript + Tailwind v4 + shadcn/ui + Radix + Motion). Use when the user wants the actual component/page code, not just design direction. Produces clean, typed, accessible, state-complete components.
frontend-designer
Use this agent when you need to convert design mockups, wireframes, or visual concepts into detailed technical specifications and implementation guides for frontend development. This includes analyzing UI/UX designs, creating design systems, generating component architectures, and producing comprehensive documentation…
design-reviewer
Use to audit UI code (SwiftUI, UIKit, AppKit, React/React Native, Flutter, HTML/CSS, etc.) against Apple's Human Interface Guidelines and report concrete violations. Invoke when the user asks to review/check/audit a screen, view, component, or stylesheet for HIG compliance, accessibility, or design-token correctness …