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 manegit 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/mane)<a href="https://agentmods.dev/skills/aimeos/pagible/mane"><img src="https://agentmods.dev/badge/skills/aimeos/pagible/mane/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/mane"><img src="https://agentmods.dev/badge/skills/aimeos/pagible/mane.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.00036 | $0.01061 |
| Opus 5.5 | $0.00014 | $0.00424 |
| Sonnet 5.5 | $0.00007 | $0.00212 |
| Haiku 4.5 | $0.00004 | $0.00106 |
Grade A, and why
mane 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mane Theme Design System
Direction
Use a calm, light and airy layout that feels like the salon itself: lots of white space, soft daylight photos and few, confident words. Put booking, the services with prices, the team and the address first, followed by what makes the salon special: results, specialities such as colour or curls, the care products and the ethos. Show real hair results, hands at work, the salon interior and the stylists as portraits; avoid stock photos with heavy make-up, retouched before and after collages, cluttered product shots and brand logos.
Foundations
- Use only the markup and classes supplied by
./theme/views/. - Use system fonts (serif display headings, sans-serif body) and the existing
--pico-*variables. - Keep page content within a
1280pxmaximum width. - Use the ivory (
#F7F2EC) background, espresso (#1F1A17) for text, filled buttons and the footer, clay rose (#9A5A43) for links, lines, icons and italic accents in headings, and blush (#E9D5CB) for the top bar, highlight boxes and badges. - Use soft
1remcorners, arched portrait images, pill buttons and hairline borders instead of shadows; labels are uppercase and letter-spaced.
Components
- Hero: a bright full width
backgroundimage in 16:9 with the subject in the right 55% and a light, calm left side (white walls, pale fabric) for the dark text without an overlay; it fills the hero from 1200px and stacks below the text on smaller screens, so keep the left 45% free of hair, faces and dark objects to meet WCAG AA (the home page adds thezoomanimation), an eyebrow naming the salon and district, a short headline with an italic accent and two actions ("Book now" and "Services & prices"). Nest secondary pages (colour, bridal, careers) below a top-level page so the header keeps about six links next to "Book now". - Figures and badges: cards in the
figureslayout for opening year, rating, team size and vegan colour, and in thebadgeslayout with clay line icons for consultation, vegan colour, clear prices, head spa and the satisfaction promise. - Signature services: a
pricingelement with three services, each with a photo, the starting price and what is included, the middle one highlighted with a badge. - Before and after: a
before-afterelement with the same client before and after a colour service; never use photos of different people. - Price list: a table with prices by stylist level and
pricingelements as price lists, one item per category, features as list items ending with a bold price and tags such asbestselleror20 minas inline code, followed by a text element with the consultation, patch test and long hair notes. - Team: cards in four columns with arched 4:5 portraits, the name as title and a bold first line with the role and speciality.
- Bridal, gift cards and careers:
pricingorcardselements with three items, one highlighted with a badge, and a horizontal timeline for the steps. - Hair tips:
blogpages below the hair tips page (status 2, hidden in navigation), each with an article, key figures, a vertical step timeline, questions and a call to action. - Visit: a hero with the salon, a table with opening hours and last appointments, cards for the salon areas, a map with directions and questions about parking, public transport, accessibility and pets.
- Footer: salon, client and company links and a newsletter card; the layout adds the address, opening hours and notice from the salon config below it.
- Salon details: the
salonconfig adds the salon JSON-LD, the announcement top bar, the "Book now" button in the header, the footer address, hours and notice and the action bar for phones.
What ships with it
60 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 698 B
- database/seeders/ManeDemo.php 72 KB
- i18n/af.po 1.7 KB
- i18n/ar.po 1.9 KB
- i18n/az.po 1.7 KB
- i18n/bg.po 2.0 KB
- i18n/ca.po 1.7 KB
- i18n/cs.po 1.7 KB
- i18n/da.po 1.6 KB
- i18n/de.po 1.6 KB
- i18n/el.po 2.0 KB
- i18n/en.po 1.6 KB
- i18n/es.po 1.7 KB
- i18n/et.po 1.6 KB
- i18n/fa.po 2.0 KB
- i18n/fi.po 1.6 KB
- i18n/fr.po 1.7 KB
- i18n/he.po 1.7 KB
- i18n/hr.po 1.7 KB
- i18n/hu.po 1.7 KB
- i18n/id.po 1.6 KB
- i18n/it.po 1.7 KB
- i18n/ja.po 1.8 KB
- i18n/km.po 2.4 KB
- i18n/ko.po 1.6 KB
- i18n/lt.po 1.7 KB
- i18n/lv.po 1.6 KB
- i18n/messages.pot 1.2 KB
- i18n/nl.po 1.6 KB
- i18n/no.po 1.6 KB
- i18n/pl.po 1.7 KB
- i18n/pt-BR.po 1.8 KB
- i18n/pt.po 1.6 KB
- i18n/ro.po 1.7 KB
- i18n/ru.po 2.0 KB
- i18n/sk.po 1.7 KB
- i18n/sl.po 1.6 KB
- i18n/sr.po 2.0 KB
- i18n/sv.po 1.6 KB
- i18n/th.po 2.1 KB
- i18n/tr.po 1.7 KB
- i18n/uk.po 2.0 KB
- i18n/vi.po 1.7 KB
- i18n/zh-TW.po 1.6 KB
- i18n/zh.po 1.6 KB
- lang/af.json 174 B
- lang/ar.json 214 B
- lang/az.json 210 B
- lang/bg.json 235 B
- lang/ca.json 178 B
- lang/cs.json 188 B
- lang/da.json 180 B
- lang/de.json 199 B
- lang/el.json 268 B
- lang/en.json 173 B
- lang/es.json 176 B
- lang/et.json 188 B
- lang/fa.json 257 B
- lang/fi.json 184 B
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 · 47 lines · 36 tokens per session scan A ed0395d07c24
mane is a skill published in the GitHub repository aimeos/pagible (596 stars, last pushed today), licensed MIT. It adds 36 tokens to every session and 1,061 once invoked, about $0.0001 per session on Opus 5.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-10-11.
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.
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"…
strapi-cms
Customisable headless CMS with Strapi.
api-design
Applies REST and GraphQL design principles to produce or review an API contract.
api-integration-architect
Design, implement, debug, and optimize API integrations with expert-level patterns for REST, GraphQL, webhooks, and authentication flows.
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…