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.
npx skills add Undertone0809/rudder --skill rudder-ui-polish-maintainergit clone --depth 1 https://github.com/Undertone0809/rudderWrote 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/skills/undertone0809/rudder/rudder-ui-polish-maintainer)<a href="https://agentmods.dev/skills/undertone0809/rudder/rudder-ui-polish-maintainer"><img src="https://agentmods.dev/badge/skills/undertone0809/rudder/rudder-ui-polish-maintainer/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/skills/undertone0809/rudder/rudder-ui-polish-maintainer"><img src="https://agentmods.dev/badge/skills/undertone0809/rudder/rudder-ui-polish-maintainer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 67 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00055 | $0.01939 |
| Opus 5 | $0.00028 | $0.00970 |
| Sonnet 5 | $0.00011 | $0.00388 |
| Haiku 4.5 | $0.00006 | $0.00194 |
Grade A, and why
rudder-ui-polish-maintainer 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.
How it starts
The opening of the file, as written. The whole thing — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rudder UI Polish Maintainer
Use this skill to turn concrete Rudder UI feedback into a scoped, implemented, validated, and committed change.
The goal is not a full redesign. The goal is to preserve Rudder's dense, operator-focused interface while fixing the specific visual or interaction problem the user noticed.
Use When
Use this skill for Rudder UI tasks such as:
- screenshot-driven visual polish
- alignment, line-height, spacing, density, overflow, or hover fixes
- adding a small status badge, label, icon, menu, or affordance
- simplifying settings sections or redundant explanatory copy
- removing a page or route that no longer belongs in the product
- changing an empty state, onboarding step, tutorial jump, or small workflow surface
- producing a quick screenshot of the current UI after a local change
- explaining why a visible surface looks wrong when the user asks "为什么" and the likely answer is current CSS/layout/data layering rather than an approved implementation request
Use build-advisor first when the user explicitly asks "你懂我要怎么改吗",
"先说说", or otherwise wants the product/design direction before edits.
After the direction is accepted, continue here for implementation.
Use advisor-review-loop-maintainer instead when the user asks for reviewer
agents, two rounds, proposal review, or an acceptance gate before handoff.
When the user invokes advisor-review-loop-maintainer for a small visible fix
but only asks to "修一下", "优化一下", "去掉这个 button", "颜色不对", or similar,
treat this skill as the implementation contract after a short advisor check.
Say explicitly in the handoff that the work used a lightweight route rather
than a full two-reviewer loop.
Do Not Use When
Do not use this skill for:
- broad architecture refactors or large feature builds
- pure code review with no UI change
- data diagnosis where the core question is "why is this page empty"; use
rudder-data-path-diagnostician-maintainer - screenshot/demo data creation; use
mock-data-maintainerand thenlanding-proof-shots-maintainerwhen needed - release, CI, Desktop packaging, or browser automation infrastructure issues
- UI Lab, component inventory, component fixture coverage, or design-system
catalog work where the main deliverable is coverage and classification rather
than a narrow rendered-state polish fix; route through
development-lifecycle-router-maintainerfirst
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 210 lines · 55 tokens per session scan A d2031e6794ff
rudder-ui-polish-maintainer is a skill published in the GitHub repository Undertone0809/rudder (288 stars, last pushed today), licensed Apache-2.0. It adds 55 tokens to every session and 1,939 once invoked, about $0.0003 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 skills, from other repositories
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
frontend-ui-dark-ts
Build dark-themed React applications using Tailwind CSS with custom theming, glassmorphism effects, and Framer Motion animations. Use when creating dashboards, admin panels, or data-rich interfaces with a refined dark aesthetic.
reveal-hover-effect
Build cursor-following spotlight reveals that expose a second aligned image through a soft radial mask. Use for hover-to-color, before-and-after, x-ray, material, texture, product-detail, and illustrated hero effects where a desaturated or embossed base image should remain visible while another treatment follows an…
frontend-visual-qa
Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.