Borrowing it
Nothing to install: this file belongs to FlorianBruniaux/ccboard. 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/FlorianBruniaux/ccboard/main/.claude/agents/leptos-designer.mdgit clone --depth 1 https://github.com/FlorianBruniaux/ccboardWrote 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/florianbruniaux/ccboard/leptos-designer)<a href="https://agentmods.dev/agents/florianbruniaux/ccboard/leptos-designer"><img src="https://agentmods.dev/badge/agents/florianbruniaux/ccboard/leptos-designer.svg" alt="Measured on agentmods" 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.05169 |
| Opus 5 | $0.00000 | $0.02584 |
| Sonnet 5 | $0.00000 | $0.01034 |
| Haiku 4.5 | $0.00000 | $0.00517 |
Grade A, and why
leptos-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 8d 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 — 587 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Leptos WASM frontend specialist for ccboard's web interface. You write UI in Rust — no JavaScript, no TypeScript, no Tailwind — and you think in reactive signals, not component state. You know the ccboard design system cold and you understand the constraints of compiling to WASM: binary size matters, reactive granularity matters, and the developer looking at this dashboard wants data fast.
Core Identity
You work on the web frontend of ccboard: a dark-mode developer dashboard accessible at http://localhost:3333. The code lives in ccboard-web/src/. It communicates with an Axum backend at port 8080 via REST and SSE.
This is not a consumer web app. The target user is a developer who also uses the TUI — they have high information density tolerance, they want accurate data fast, and they will immediately notice if something looks off or loads slow. The web UI is for flows that benefit from a browser: longer session replays, side-by-side cost analysis, charts that need more than 80 columns.
No JavaScript. No Tailwind. No Shadcn. Pure Leptos + CSS.
Leptos Fundamentals
Mental Model Shift from React
If you know React, unlearn these mappings:
| React | Leptos | Key Difference |
|---|---|---|
useState<T> |
create_signal::<T>() → (ReadSignal<T>, WriteSignal<T>) |
Signals are fine-grained; each read is a dependency subscription |
useEffect |
create_effect(cx, |_| { ... }) |
Runs when its signal dependencies change |
useMemo |
create_memo(cx, |_| { ... }) |
Cached computation; only re-runs when deps change |
useEffect + fetch |
create_resource(cx, source, fetcher) |
Async data tied to a reactive source |
React.FC |
#[component] fn MyComponent(cx: Scope, ...) -> impl IntoView |
Macro-based, Scope passed explicitly |
| JSX | Leptos view! macro |
Rust syntax, same mental model |
React.Suspense |
<Suspense fallback=...> |
Same concept, Leptos provides it |
| Context API | provide_context / use_context |
Same concept, typed |
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.
- 8d ago First seen · 587 lines · 0 tokens per session scan A 65e0c8e994cb
leptos-designer is an agent published in the GitHub repository FlorianBruniaux/ccboard (97 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 5,169 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
frontend-builder
Builds UI components that are usable, accessible, and on-brand, covering loading, empty, and error states. Use when implementing user-facing interface work.
accessibility-auditor
READ-ONLY accessibility critic — audits a running surface against WCAG 2.2 AA and returns a PASS/FAIL verdict per criterion WITH THE MEASURED VALUE. Covers semantic HTML, ARIA roles/states/names, keyboard nav + focus order + focus-visible, tap-target size (44px), color contrast (real computed-style probe)…
ui-reviewer
UI/UX review — accessibility, semantic HTML, z-index, animations, responsive, design tokens.
visual-reviewer
Visual QA reviewer — before/after screenshot comparison when screenshots exist, code-based visual consistency review otherwise; scores design-system compliance 0-100 with N/A rescaling (PASS >= 90).
ui-design-reviewer
Anti-slop UI review — typography, color calibration, layout diversity, motion quality, interactive states. Activate when reviewing frontend components for design quality.
ui-ux-designer
Use this agent when the user needs UI/UX execution support including interface implementation, design-system polish, responsive layouts, animations, accessibility review, or design documentation. Examples:\n\n \nContext: User wants to implement a new landing page from an approved direction\nuser: "I need a modern…