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 xsolla/xsolla-ai-kit --skill login-stylinggit clone --depth 1 https://github.com/xsolla/xsolla-ai-kitWrote 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/xsolla/xsolla-ai-kit/login-styling)<a href="https://agentmods.dev/skills/xsolla/xsolla-ai-kit/login-styling"><img src="https://agentmods.dev/badge/skills/xsolla/xsolla-ai-kit/login-styling/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/xsolla/xsolla-ai-kit/login-styling"><img src="https://agentmods.dev/badge/skills/xsolla/xsolla-ai-kit/login-styling.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.00250 | $0.02022 |
| Opus 5 | $0.00125 | $0.01011 |
| Sonnet 5 | $0.00050 | $0.00404 |
| Haiku 4.5 | $0.00025 | $0.00202 |
Grade A, and why
login-styling 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.
How it starts
The opening of the file, as written. The whole thing — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Owner: Elnur Khalilov (Login FE) · Last verified: July 2026 · Applies to: Login Widget 2.0 (
login-widget-ng) + Publisher Account Login module. This skill's primary, recommended path is Channel 3 — CSS deployed via API. The other three channels (PA editor, PA CSS upload, SDK) are documented inreferences/channels-and-flag.md.
When to use
Use this skill — always alongside login-setup — when the Login UI
must look on-brand rather than shipping the Xsolla default:
- Deploy arbitrary custom CSS to the Login widget via API (no Publisher Account clicking) — the main flow below
- Apply the game's brand tokens (colors, logo, roundness, background, fonts) to the sign-in, sign-up, and password-reset screens
- White-label / dark-mode the login experience
- Choose between API CSS, Publisher Account CSS, structured
themeJSON, and SDKcustomStyle
Out of scope: wiring the auth flow, OAuth clients, JWT validation (→
login-setup); catalog/storefront visuals (→ catalog-design);
checkout/payment UI styling (→ headless-checkout-integration). CSS cannot change the
widget's layout/structure or inject HTML/JS — see limitations.
Prerequisites
export XSOLLA_MERCHANT_ID=<numeric merchant ID> # e.g. 71070
export XSOLLA_PROJECT_ID=<numeric publisher project ID> # e.g. 300837
export XSOLLA_LOGIN_PROJECT_ID=<login project UUID> # e.g. 2f1ba87f-...
export XSOLLA_PUBLISHER_TOKEN=<Publisher Account bearer token>
- A working Login integration from
login-setup— the widget must render before it can be styled. - Signed Xsolla Product Licensing Agreement (PA → Agreements). Widget customization (CSS upload / editor Save) is disabled until it is signed.
- Login Widget 2.0 (
widget_generation > 0). The legacy widget (=== 0) uses a different, limited endpoint — seereferences/channels-and-flag.md. - Xsolla MCP (recommended). These are the exact endpoints the PA frontend itself calls;
they are reliable but not a formally published public API. Verify current shapes with
search_xsolla_sources(or the linked docs) before handing them to a partner as official.
What ships with it
2 files 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.
- 9d ago First seen · 132 lines · 250 tokens per session scan A 7062dc212bb9
login-styling is a skill published in the GitHub repository xsolla/xsolla-ai-kit (3 stars, last pushed 21d ago), licensed MIT. It adds 250 tokens to every session and 2,022 once invoked, about $0.0013 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-31.
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-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.
animation-principles
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use motion-system (design-systems); for a full interaction spec use micro-interaction-spec.
refactoring-ui
Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions "my UI looks off" (or amateur/unprofessional), "fix the design", "Tailwind styling", "color palette", "visual hierarchy", "design system", "spacing scale", or "component styling". Also trigger when building consistent…