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 aimeos/pagible --skill luxurygit clone --depth 1 https://github.com/aimeos/pagibleWrote 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/aimeos/pagible/luxury)<a href="https://agentmods.dev/skills/aimeos/pagible/luxury"><img src="https://agentmods.dev/badge/skills/aimeos/pagible/luxury/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/aimeos/pagible/luxury"><img src="https://agentmods.dev/badge/skills/aimeos/pagible/luxury.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00029 | $0.02014 |
| Opus 5 | $0.00015 | $0.01007 |
| Sonnet 5 | $0.00006 | $0.00403 |
| Haiku 4.5 | $0.00003 | $0.00201 |
Grade A, and why
luxury 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Luxury Theme Design System
Mission
You are an expert frontend developer for the Luxury theme. Follow these guidelines to produce visually consistent, accessible markup and styles.
Brand
Restrained, editorial, high-fashion. Warm ivory background (#FBF9F4) with near-black text (#1C1A16) and sparing antique gold accents (#7A5F32). High-contrast serif display headlines, geometric sans-serif body, uppercase letter-spaced labels, sharp (zero-radius) edges, hairline rules, flat surfaces and abundant whitespace. The aesthetic is monochrome with a single gold reveal on interaction. Built on Pico CSS with --pico-* custom property overrides.
Style Foundations
- Visual style: minimalist luxury / fashion editorial. No texture, pattern or heavy shadow; flat surfaces, hairline borders, generous negative space. Gold is decorative and rare — never a fill on large areas
- Typography: Body font=Futura, 'Century Gothic', 'Avenir Next', 'Helvetica Neue', Helvetica, Arial, sans-serif | Display font (headings/brand)=Didot, 'Bodoni 72', 'Bodoni MT', 'Bodoni Moda', 'Playfair Display', 'Hoefler Text', Garamond, 'Times New Roman', serif | Monospace=ui-monospace, monospace | weights=400 (h1-h3/brand/body), 500 (h4-h6/nav/labels/buttons) | Base size: 1.1875rem | Sizes use calc(var(--pico-font-size) * multiplier): h1=2.5x/3x(768px)/2.85x(hero)/4.25x(hero 768px), h2=1.7x/2x(768px), h3=0.95x, h4=0.82x | line-height: body=1.7, h1=1.08, h2=1.18, hero h1=1.04 | letter-spacing: headings=0.005em, hero h1=0.01em, body/.text=0.01em, nav=0.14em, brand=0.22em, buttons/labels=0.15em, eyebrow=0.32em — serif display headings are NOT negatively tracked
- Color tokens: --pico-color=#1C1A16, --pico-background-color=#FBF9F4, --pico-muted-color=#6E6557, --pico-muted-border-color=#1C1A1618, --pico-muted-background-color=#F3EEE4, --pico-contrast=#1C1A16, --pico-contrast-background=#FFFFFF, --pico-contrast-inverse=#FFFFFF, --pico-primary=#1C1A16 (near-black: links + primary CTA fill), --pico-primary-hover=#8A6E3F (gold reveal), --pico-secondary=#7A5F32 (antique gold accent), --pico-secondary-hover=#5F4A26, --pico-text-selection-color=#B79A5E40 | Surfaces: #FFFFFF cards, #F3EEE4 alternating sections, #1C1A16 footer | Heading colors: h1-h4=#1C1A16, h5=#3A352B, h6=#6E6557
- Border radius: --pico-border-radius=0 — everything is sharp-cornered (buttons, inputs, cards, images, containers). Do NOT introduce rounded corners | Shadows: kept faint and flat. box-shadow: 0 1px 2px #1C1A1608, 0 1px 1px #1C1A1605; card hover: 0 1rem 2.5rem #1C1A160F; drop-shadow (image/video/slideshow): 0 1.5rem 3rem #1C1A1614
- Max widths: 1280px (header/footer/page/docs/blog), 1200px (main container), 960px (CMS content), 50rem (text), 38rem (hero paragraph) | Section padding: 5.5rem / 8rem(768px); hero 9rem 0 7rem(768px) | Breakpoints: 576px, 768px, 992px, 1024px
- Components: hero (huge serif headline, gold uppercase eyebrow subtitle with a centered hairline rule below — NO pill badge), cards (1->3 col grid, flat hairline border, serif title, subtle hover lift), heading (centered h1/h2 with a 3rem gold hairline rule beneath via ::after), blog (featured+list with serif date), questions/FAQ accordion, contact form (gold focus ring), toc, slideshow, article, search dialog, docs sidebar (20rem, sticky), near-black footer
- Buttons: sharp (0 radius), uppercase, letter-spacing 0.15em, sans-serif label at 0.72x | Default=transparent with 1px near-black border, inverts to solid near-black on hover | Primary (.btn:first-child / nav CTA)=near-black fill, white text, fills gold (#8A6E3F) on hover | Padding: 1rem 2.25rem
What ships with it
27 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.
- .gitattributes 60 B
- composer.json 675 B
- database/seeders/LuxuryDemo.php 62 KB
- LICENSE 1.0 KB
- public/article.css 331 B
- public/cards.css 1.2 KB
- public/cms-lazy.css 8.4 KB
- public/cms.css 12 KB
- public/contact.css 2.2 KB
- public/hero.css 3.2 KB
- public/image-text.css 1.8 KB
- public/image.css 434 B
- public/layout-blog.css 174 B
- public/layout-docs.css 2.5 KB
- public/layout-page.css 1.3 KB
- public/list.css 3.0 KB
- public/pricing.css 5.0 KB
- public/questions.css 1.4 KB
- public/slideshow.css 11 KB
- public/table.css 1.9 KB
- public/testimonial.css 1.9 KB
- public/toc.css 808 B
- public/video.css 369 B
- README.md 3.0 KB
- schema.json 3.4 KB
- src/LuxuryServiceProvider.php 467 B
- views/layouts/main.blade.php 12 KB
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 · 92 lines · 29 tokens per session scan A 725a11d85182
luxury is a skill published in the GitHub repository aimeos/pagible (587 stars, last pushed yesterday), licensed MIT. It adds 29 tokens to every session and 2,014 once invoked, about $0.0001 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
api-designer
Designs production-grade APIs — REST, GraphQL, gRPC, and AsyncAPI patterns including pagination, versioning, error handling, rate limiting, and API governance. Use when the user asks to design APIs, create endpoints, build an API layer, write OpenAPI specs, or needs help with REST/GraphQL/gRPC service design.
strapi-cms
Customisable headless CMS with Strapi.
api-design-first
Design-first API development skill. Generates OpenAPI 3.1 specifications, enforces REST design best practices, validates endpoints, handles versioning, pagination, error formatting, authentication patterns, rate limiting, and idempotency. Activates when users say "design an API", "create OpenAPI spec", "API endpoint"…
api-design
Applies REST and GraphQL design principles to produce or review an API contract.
payload
Use when working with Payload projects (payload.config.ts, collections, fields, hooks, access control, Payload API). Use when debugging validation errors, security issues, relationship queries, transactions, or hook behavior.
scalar-design-system
Scalar's design system — design tokens, theming (@scalar/themes), CSS variables, and the @scalar/components library. Use when designing or implementing Scalar UI, especially with Paper (code-to-design / design-to-code), so output matches real Scalar tokens, colors, typography, spacing, and components instead of…