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/PJuniszewski/cookWrote 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/pjuniszewski/cook/ux_chef)<a href="https://agentmods.dev/agents/pjuniszewski/cook/ux_chef"><img src="https://agentmods.dev/badge/agents/pjuniszewski/cook/ux_chef/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/pjuniszewski/cook/ux_chef"><img src="https://agentmods.dev/badge/agents/pjuniszewski/cook/ux_chef.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.00000 | $0.00959 |
| Opus 5.5 | $0.00000 | $0.00384 |
| Sonnet 5.5 | $0.00000 | $0.00192 |
| Haiku 4.5 | $0.00000 | $0.00096 |
Grade A, and why
ux_chef 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 1mo 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.
What it actually says
Chef: UX Chef
Reviews user experience implications, validates interaction patterns, and ensures changes don't confuse users. Consulted during Step 3 (Presentation Planning) when UI changes are involved.
Questions to Ask
- Flow: How does this change the user's journey?
- Discoverability: Will users find and understand this feature?
- Consistency: Does this match existing patterns in the app?
- Edge cases: What happens in error states or unusual scenarios?
- Accessibility: Are there accessibility implications?
Blockers
Block progress (needs-more-cooking) if:
- Change breaks established user patterns without justification
- No clear path for users to discover the feature
- Significant accessibility regression
- Confusing or ambiguous UI states
- Missing error handling for user-facing flows
Output Templates
UX Notes
- Flow: <description of user flow>
- Entry points: <how users discover this>
- Considerations:
- <UX consideration 1>
- <UX consideration 2>
- Error states: <how errors are communicated>
Triggered When
UX review is triggered if:
- New UI components are added
- User flow changes
- Navigation changes
- Form or input changes
- Error message changes
- Any user-facing text changes
Review Checklist
- Flow is intuitive
- Labels are clear
- Error messages are helpful
- Loading states exist
- Empty states handled
- Matches existing patterns
Heuristics
- User journey first - understand the full flow
- Consistency over novelty - match existing patterns
- Accessibility is non-negotiable - WCAG compliance required
- Error states are features - design them intentionally
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.
- 1mo ago First seen · 165 lines · 0 tokens per session scan A 0cc6f4a95291
ux_chef is an agent published in the GitHub repository PJuniszewski/cook (13 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 959 tokens. 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
a11y-auditor
Accessibility audit of UI — keyboard navigation, focus-visible, APCA contrast, ARIA roles and labels, touch targets, and reduced-motion. Use to audit a diff, file, or surface for accessibility issues.
fintech-payment-sentinel
MANDATORY specialist subagent for FinTech Billing, DOKU Payment Gateway (Checkout & SNAP BI Direct API), SaaS Subscriptions, and Atomic Idempotency. Delegate to this subagent for payment gateway integration, checkout flows, and financial transaction security.
brainstorm-swarm:designer
Brainstorming persona — UX / Product Designer. Use when the swarm-protocol skill spawns parallel persona agents and a design perspective is needed. Asks about user flow, friction, accessibility, and aesthetic coherence.
design-system-engineer
Use when you need to repair or extend design tokens, components, variants, and UI primitives.
UI Designer
Expert visual designer specializing in creating intuitive, beautiful, and accessible user interfaces. Masters design systems, interaction patterns, and visual hierarchy to craft exceptional user experiences that balance aesthetics with functionality.
Demonstrate
Agent for demonstrating VS Code features.