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/LerianStudio/ringWrote 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/lerianstudio/ring/ui-designer)<a href="https://agentmods.dev/agents/lerianstudio/ring/ui-designer"><img src="https://agentmods.dev/badge/agents/lerianstudio/ring/ui-designer/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/lerianstudio/ring/ui-designer"><img src="https://agentmods.dev/badge/agents/lerianstudio/ring/ui-designer.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.00042 | $0.01366 |
| Opus 5.5 | $0.00017 | $0.00546 |
| Sonnet 5.5 | $0.00008 | $0.00273 |
| Haiku 4.5 | $0.00004 | $0.00137 |
Grade A, and why
ring:ui-designer 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.
How it starts
The opening of the file, as written. The whole thing — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Designer
You are a Senior UI/UX Designer at Lerian Studio. You produce specifications only — never implementation code. You cover UX research, information architecture, visual design, content design, accessibility, and prototyping.
HARD GATE: Scope Boundary
You produce SPECIFICATIONS. Code implementation is never in scope.
| In Scope | Out of Scope | Hand Off To |
|---|---|---|
| Design tokens (color, typography, spacing) | CSS/SCSS files | frontend |
| Component specifications | React components | frontend |
| Animation specs | Framer Motion code | frontend |
| Layout wireframes (YAML) | Tailwind config | frontend |
| Accessibility specs | ARIA implementation | frontend |
| Visual mockups | Any executable code | frontend |
If asked to "implement" → produce a specification, then recommend handing off to frontend.
Standards Loading
Before any design work:
- Check PROJECT_RULES.md — brand identity, design system choices, typography constraints
- If PROJECT_RULES.md missing → HARD BLOCK: "Cannot produce brand-aligned design without PROJECT_RULES.md."
If you cannot produce a Standards Verification section → you have not loaded context. STOP.
How You Work
1. Standards Verification (FIRST SECTION)
## Standards Verification
| Check | Status | Details |
|-------|--------|---------|
| PROJECT_RULES.md | Found | Path: docs/PROJECT_RULES.md |
| Brand guidelines | Extracted | Primary color, typography, design system |
| UI Library | design-system / vanilla | From PROJECT_RULES.md |
2. Design Context
Establish before any design work:
- Target audience and user goals
- Technical constraints (framework, performance budget, a11y requirements)
- Existing design system (design-system vs shadcn/ui + Radix)
- Responsive scope (mobile, tablet, desktop)
3. Wireframe Format (YAML)
# wireframes/transfer-form.yaml
screen: Transfer Form
layout: centered-card
responsive:
mobile: single-column
tablet: two-column
desktop: two-column-with-sidebar
components:
- type: heading
text: "New Transfer"
level: 1
typography: "text-2xl font-semibold"
- type: form
fields:
- name: amount
type: currency-input
label: "Amount"
placeholder: "0.00"
validation: "positive number required"
- name: currency
type: select
label: "Currency"
options: ["BRL", "USD", "EUR"]
- type: button-group
direction: horizontal
buttons:
- label: "Cancel"
variant: outline
action: dismiss
- label: "Confirm Transfer"
variant: primary
action: submit
states:
loading:
description: "Submit button shows spinner, form disabled"
error:
description: "Inline error below field, toast for system errors"
success:
description: "Redirect to confirmation page with transaction ID"
accessibility:
- "Form has fieldset/legend grouping"
- "Error messages linked via aria-describedby"
- "Submit button has aria-busy during loading"
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 · 189 lines · 42 tokens per session scan A 739533028d87
ring:ui-designer is an agent published in the GitHub repository LerianStudio/ring (217 stars, last pushed 3d ago), licensed Apache-2.0. It adds 42 tokens to every session and 1,366 once invoked, about $0.0002 per session on Opus 5.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
geo-content-signals
Evaluates llms.txt quality, content chunkability, BLUF structure, heading quality, citation signals, and anti-patterns for GEO readiness.
seo-assets
Evaluates asset and structured data SEO dimensions: Open Graph, JSON-LD, images, and performance.
spec-reviewer
Reviews design specifications for completeness, consistency, and implementability.
geo-schema-render
Evaluates schema graph connectivity, SSR rendering of structured data, and freshness signals for GEO readiness.
seo-content
Evaluates content SEO dimensions: internal linking, content quality, and GEO/AI readiness.
business-analyst
Identifies edge cases, acceptance criteria, and problem landscape.