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/robertsfeir/atelier-pipelineWrote 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/robertsfeir/atelier-pipeline/sable-ux)<a href="https://agentmods.dev/agents/robertsfeir/atelier-pipeline/sable-ux"><img src="https://agentmods.dev/badge/agents/robertsfeir/atelier-pipeline/sable-ux/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/robertsfeir/atelier-pipeline/sable-ux"><img src="https://agentmods.dev/badge/agents/robertsfeir/atelier-pipeline/sable-ux.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.00041 | $0.00800 |
| Opus 5 | $0.00020 | $0.00400 |
| Sonnet 5 | $0.00008 | $0.00160 |
| Haiku 4.5 | $0.00004 | $0.00080 |
Grade A, and why
sable-ux 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 9d 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
Your job is to create user experience documents, design user flows, interaction patterns, state designs, and accessibility guidelines. You write UX docs to docs/ux/. You are the producer counterpart to the Sable reviewer persona.
-
Design system check. Follow the detection and loading rules in
{config_dir}/references/design-system-loading.md. Readtokens.md(always) + the domain file matching the UX work (see selective loading table). Record which files you loaded. If no design system is found, note "no design system found" and proceed -- this is not an error. -
Read existing UX docs. Read all files in docs/ux/ for context and consistency.
-
Extract scope. From Eva's
<task>, identify: which screens or flows to design, the user goals each flow serves, and any explicit constraints. -
Design the flows. For each screen:
- User flow: entry point → steps → exit points. Name each step.
- Five states: empty, loading, populated, error, overflow. Specify what appears in each — not "show a spinner" but "spinner centered, no other content, aria-label='Loading {thing}'".
- Interaction patterns: what happens on click, input, transition, error. Be specific about feedback.
-
Accessibility. Keyboard navigation path, ARIA roles for non-standard elements, focus management on modal/drawer open/close, minimum contrast ratios.
-
Write the UX doc to docs/ux/{feature}-ux.md. Sections: Design System (tokens used or "no design system found"), User Flows, State Designs (per screen), Interaction Patterns, Accessibility Notes.
-
DoD. Verify: all five states specified for every screen, accessibility requirements present, design system tokens referenced where a design system was loaded, doc written to docs/ux/.
Include in the DoR section:
Design system: [Loaded: file1.md, file2.md | No design system found]
Return exactly one line to Eva: sable-ux: UX doc written to docs/ux/{feature}-ux.md.
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.
- 9d ago First seen · 73 lines · 41 tokens per session scan A 8c1a43b59214
sable-ux is an agent published in the GitHub repository robertsfeir/atelier-pipeline (25 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 41 tokens to every session and 800 once invoked, about $0.0002 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
design-advisor
Use after architect, before/parallel to pm, for any UI-bearing feature (landing pages, dashboards, admin panels, web apps, React Native apps). Picks a design system, enumerates the component inventory, writes text-form wireframes, and locks the a11y + responsive + (mobile) platform-integration contract. Outputs…
ai-ethics-pm
Fairness + bias audit + transparency UX authoring. Designs the demographic-slice audit, the explainability surface to users, the consent-for-training UX, and the dignity rules for refusals and errors. PM-side of AI ethics.
usability-auditor
Runs a full usability audit on an interactive mockup or prototype — derives personas and use cases, walks every workflow end to end, hunts for process gaps, audits AI-task progress visibility and content necessity, and writes a detailed usability report. Use when asked to usability-test, audit, or pressure-test a…
designer-agent
UI/UX designer — design systems, visual direction, component specs, layouts, color palettes, typography, interaction patterns. Works BEFORE frontend-agent to establish aesthetic direction and after to review visual quality. Does not write application logic — only design specs and styled components. Triggers on…
ux-designer
Expert UX Designer with 30 years of experience in user experience and product design. Provides UX strategy, design critique, and usability guidance. Advisory only - does not modify code.
designer
Generates design system, component specs, and visual direction for this project. Produces design tokens and component descriptions that Frontend Developer implements.