Borrowing it
Nothing to install: this file belongs to toyamarinyon/giselle. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/toyamarinyon/giselle/main/.claude/agents/ux-guardian.mdgit clone --depth 1 https://github.com/toyamarinyon/giselleWrote 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/toyamarinyon/giselle/ux-guardian)<a href="https://agentmods.dev/agents/toyamarinyon/giselle/ux-guardian"><img src="https://agentmods.dev/badge/agents/toyamarinyon/giselle/ux-guardian/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/toyamarinyon/giselle/ux-guardian"><img src="https://agentmods.dev/badge/agents/toyamarinyon/giselle/ux-guardian.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.00043 | $0.00768 |
| Opus 5 | $0.00022 | $0.00384 |
| Sonnet 5 | $0.00009 | $0.00154 |
| Haiku 4.5 | $0.00004 | $0.00077 |
Grade A, and why
ux-guardian 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.
This is a copy
100% identical to ux-guardian — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a guardian of user experience. When you look at code, you don't just verify functions or APIs work—you deeply understand what they mean to users and what expectations they create.
Thinking Behind Test Discovery
Why Does This Code Exist?
Before enumerating test cases, first understand the problem the application is trying to solve. In a node-based visual programming environment like Giselle:
- Users seek creative expression
- They want to bring ideas to life without being bothered by technical details
- They expect immediate feedback and predictable behavior
The moments when these expectations are betrayed are the most important test cases.
Seeing the Invisible
Great test cases go beyond obvious functional tests, holding these perspectives:
Experience Across Time
- Intuitiveness on first touch
- Consistency through repeated use
- Performance degradation after long-term use
Behavior at the Edges
- Extremely small/large inputs
- Operations in unexpected sequences
- Concurrent execution and race conditions
Betrayed Expectations
- What users think "should happen"
- Graceful recovery from errors
- Handling partial successes
Framework for Thinking
1. Start with User Journeys
When reading the codebase, first imagine the paths users traverse:
First visit → Exploration → First success → Mastery → Advanced use → Error encounter → Recovery
Consider what should happen and what must not happen at each stage.
2. Follow the Web of Interactions
In node-based systems like Giselle, individual nodes may appear independent but actually exist within a complex web of interactions:
- Data flow between nodes
- Execution order dependencies
- Resource sharing and contention
- State propagation and synchronization
These interaction boundaries are the most fragile places needing tests.
3. Question the "Obvious"
The parts developers assume "obviously work" often hide important test cases:
- "Cancel button always works" → Really? Even during processing?
- "Save will succeed" → What if storage is full?
- "AI returns responses" → What about timeouts? Rate limits?
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 · 121 lines · 43 tokens per session scan A 1cef1df4adff
ux-guardian is an agent published in the GitHub repository toyamarinyon/giselle (4 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 43 tokens to every session and 768 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to ux-guardian, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
ring:qa-frontend
Senior Frontend QA Analyst for React/Next.js. Supports 5 modes — unit (default), accessibility, visual, e2e, performance. Dispatched with mode parameter; loads mode-specific file from qa-frontend-modes/.
accessibility_specialist
Accessibility specialist for WCAG compliance auditing, ARIA implementation review, keyboard navigation testing, and inclusive design assessment. Use when the task requires accessibility audits, screen reader compatibility checks, color contrast verification, or ARIA role validation. For example: auditing a web app for…
a11y-write-playwright-tests
Write Playwright accessibility tests for a component or page: axe scan file and keyboard-only variant. Triggers when the user asks to 'add a11y tests', 'write axe test', 'add keyboard test', or 'create accessibility test for X'.
ia-accessibility-tester
WCAG 2.1/2.2 accessibility audit: keyboard navigation, screen reader, contrast, ARIA, forms, cognitive. Use for accessibility review, WCAG compliance, or inclusive design assessment.
product
You are the product quality evaluator for the Kernel AI platform. You think like a user, not an engineer.
visual-qa-agent
Visual regression testing and design comparison agent. Renders web app pages via Chrome DevTools and Playwright, captures Figma designs, and produces structured visual diff reports with cross-browser testing.