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 agentmods add skills/aimeos/pagible/stylenpx skills add aimeos/pagible --skill stylegit 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/style)<a href="https://agentmods.dev/skills/aimeos/pagible/style"><img src="https://agentmods.dev/badge/skills/aimeos/pagible/style.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.00033 | $0.01624 |
| Opus 5 | $0.00016 | $0.00812 |
| Sonnet 5 | $0.00007 | $0.00325 |
| Haiku 4.5 | $0.00003 | $0.00162 |
Grade A, and why
style 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 7d 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Style Theme Design System
Mission
You are an expert frontend developer for the Style theme. Follow these guidelines to produce a cinematic luxury landing feel: editorial hierarchy, high contrast on dark surfaces, oversized type, generous spacing, and a restrained call-to-action model.
Implementation constraints:
- Use only the HTML markup and classes defined in
./theme/views/. - Do not add your own utility classes in this theme.
- Use nearest OS/system fonts and avoid remote font loading.
Brand
Editorial luxury fashion commerce. Use an existing Pico-based theme palette through current --pico-* tokens, with a moody editorial feel and strong contrast.
The look should feel like a campaign home page: image-dominant hero, large typography, floating accents, rounded editorial cards, and confident uppercase action language.
Style Foundations
- Visual style: editorial luxury. Avoid flat flat-card SaaS blocks unless image-supported.
- Typography:
- Sans display and body:
system-ui,-apple-system,"Segoe UI", Arial, Helvetica, sans-serif - Mono:
ui-monospace, SFMono-Regular, Menlo, Monaco, Consolas, "Liberation Mono", "Courier New", monospace - Body base:
16pxwith generous line-height - Display scale:
140pxon desktop hero headings, responsive downscales for tablet/mobile. - Letter spacing: negative tracking for large headlines (
-1.5px), uppercase where explicit.
- Sans display and body:
- Radius and treatment:
- Use rounded visual language for major surfaces (
24px) and pill buttons. - Use subtle shadows only for depth (
shadow-2xl,shadow-xs) and ring effects with existing palette variables.
- Use rounded visual language for major surfaces (
- Spacing and layout:
- Body max width:
1280px - Horizontal inset:
px-8desktop, reduced on small screens - Section rhythm:
120pxvertical in hero and content blocks - Breakpoints:
md,lgonly; no exotic grid systems.
- Body max width:
- Component expectations:
- Hero: full-bleed image panel group with one large leading image and two offset supporting images.
- Editorial blocks: image-first narrative sections with headline + supporting paragraph.
- Footer: compact two-row nav structure with muted legal strip.
- Buttons: rounded pill styles, uppercase tracking, distinct hover states.
What ships with it
26 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 686 B
- database/seeders/StyleDemo.php 57 KB
- public/article.css 589 B
- public/cards.css 1.7 KB
- public/cms-lazy.css 8.1 KB
- public/cms.css 13 KB
- public/contact.css 1.5 KB
- public/hero.css 3.8 KB
- public/image-text.css 2.5 KB
- public/image.css 633 B
- public/layout-blog.css 313 B
- public/layout-docs.css 2.5 KB
- public/layout-page.css 957 B
- public/list.css 3.1 KB
- public/pricing.css 4.8 KB
- public/questions.css 1.4 KB
- public/slideshow.css 11 KB
- public/table.css 2.0 KB
- public/toc.css 807 B
- public/video.css 398 B
- README.md 3.0 KB
- schema.json 3.6 KB
- src/StyleServiceProvider.php 463 B
- views/hero.blade.php 2.3 KB
- 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.
- 7d ago First seen · 134 lines · 33 tokens per session scan A f01188201531
style is a skill published in the GitHub repository aimeos/pagible (586 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 1,624 once invoked, about $0.0002 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.
pinch-to-post
Create and edit posts, manage plugins and themes, configure site settings, manage users, WooCommerce orders, run governance scans, and generate content via 88+ MCP tools. Use when the user asks about WordPress tasks, blog posts, plugins, themes, WooCommerce, or site administration.
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.
lap
LAP CLI -- compile, search, and manage API specs for AI agents. Use when working with API specifications (OpenAPI, GraphQL, AsyncAPI, Protobuf, Postman), compiling specs to LAP format, searching the LAP registry, generating skills from API specs, or publishing APIs. Commands: init, compile, search, get, skill…