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 brewgit 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/brew)<a href="https://agentmods.dev/skills/aimeos/pagible/brew"><img src="https://agentmods.dev/badge/skills/aimeos/pagible/brew/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/brew"><img src="https://agentmods.dev/badge/skills/aimeos/pagible/brew.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.00033 | $0.00842 |
| Opus 5.5 | $0.00013 | $0.00337 |
| Sonnet 5.5 | $0.00007 | $0.00168 |
| Haiku 4.5 | $0.00003 | $0.00084 |
Grade A, and why
brew 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 8d 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brew Theme Design System
Direction
Use a warm, unhurried layout that makes guests want to come in. Put the menu, the opening hours, the address and the way to order ahead first, followed by what makes the place special: the coffees on offer, the bakery, the people and the farms. Show real drinks, pastries, the room and the team; avoid generic coffee bean wallpapers, stock photos of people holding takeaway cups as the main visual and brand logos on bags or cups.
Foundations
- Use only the markup and classes supplied by
./theme/views/. - Use system fonts (serif headings, monospace labels) and the existing
--pico-*variables. - Keep page content within a
1280pxmaximum width. - Use a paper (
#F7F3EC) background, espresso (#2A211C) for text, the top bar, the footer and dark sections, roast (#8A4B2A) for links, buttons and italic accents in markdown headings, and crema (#C8A165) only for dots, separators, badges and text on dark backgrounds, never for text on light backgrounds. - Use rounded cards, pill buttons and dashed separators instead of heavy shadows; labels, prices and tags are monospace and uppercase.
Components
- Hero: a paper hero with a monospace eyebrow naming the place and city, a short headline, two actions ("See the menu" and "Order ahead") and one portrait image in
files, shown with an arched top. - Figures and badges: cards in the
figureslayout for opening year, farms, fermentation hours or opening time, and in thebadgeslayout with roast line icons for roasting, direct trade, the bakery, reusable cups and low waste. - Coffees: cards with a photo, the origin as title and a text with a bold first line for process, altitude and price, followed by the tasting notes as inline code pills.
- Menu:
pricingelements as menu boards, one item per section, features as list items ending with a bold price and dietary tags as inline code, followed by a text element with the tag legend and allergen note. - Subscriptions, classes, catering and pre-order boxes:
pricingelements with three items, the middle one highlighted with a badge. - Process: horizontal timelines for farm to cup, class afternoons or ordering.
- Journal:
blogpages below the journal page, each with an article, key figures, a vertical step timeline, questions and a call to action. - Visit: a hero with the terrace or room, a table with opening hours, cards for the seating areas, a map with directions and questions about accessibility, dogs and parking.
- Footer: café, coffee and company links and a newsletter card; the layout adds the address and opening hours from the café config below it.
- Café details: the
cafeconfig adds the café JSON-LD, the announcement top bar, the "Order ahead" button in the header, the footer address and hours 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 695 B
- database/seeders/BrewDemo.php 78 KB
- i18n/af.po 2.3 KB
- i18n/ar.po 2.6 KB
- i18n/az.po 2.5 KB
- i18n/bg.po 2.9 KB
- i18n/ca.po 2.4 KB
- i18n/cs.po 2.4 KB
- i18n/da.po 2.3 KB
- i18n/de.po 2.3 KB
- i18n/el.po 2.9 KB
- i18n/en.po 2.3 KB
- i18n/es.po 2.4 KB
- i18n/et.po 2.3 KB
- i18n/fa.po 2.7 KB
- i18n/fi.po 2.3 KB
- i18n/fr.po 2.4 KB
- i18n/he.po 2.5 KB
- i18n/hr.po 2.3 KB
- i18n/hu.po 2.4 KB
- i18n/id.po 2.3 KB
- i18n/it.po 2.3 KB
- i18n/ja.po 2.5 KB
- i18n/km.po 3.2 KB
- i18n/ko.po 2.3 KB
- i18n/lt.po 2.4 KB
- i18n/lv.po 2.4 KB
- i18n/messages.pot 1.7 KB
- i18n/nl.po 2.3 KB
- i18n/no.po 2.3 KB
- i18n/pl.po 2.3 KB
- i18n/pt-BR.po 2.4 KB
- i18n/pt.po 2.3 KB
- i18n/ro.po 2.4 KB
- i18n/ru.po 2.8 KB
- i18n/sk.po 2.4 KB
- i18n/sl.po 2.3 KB
- i18n/sr.po 2.7 KB
- i18n/sv.po 2.3 KB
- i18n/th.po 3.1 KB
- i18n/tr.po 2.4 KB
- i18n/uk.po 2.8 KB
- i18n/vi.po 2.5 KB
- i18n/zh-TW.po 2.3 KB
- i18n/zh.po 2.2 KB
- lang/af.json 131 B
- lang/ar.json 159 B
- lang/az.json 164 B
- lang/bg.json 201 B
- lang/ca.json 148 B
- lang/cs.json 151 B
- lang/da.json 135 B
- lang/de.json 149 B
- lang/el.json 211 B
- lang/en.json 129 B
- lang/es.json 136 B
- lang/et.json 140 B
- lang/fa.json 187 B
- lang/fi.json 144 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.
- 8d ago First seen · 46 lines · 33 tokens per session scan A 10f86bac34c2
brew is a skill published in the GitHub repository aimeos/pagible (596 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 842 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-10.
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…