brew

brew is a skill for Claude Code, Codex from aimeos/pagible. It costs 33 tokens per session (842 once invoked), scanned A, original, MIT.

A visual design system for cafés, coffee roasters, and bakeries. It defines warm colours, typography, layout rules, page sections, and image guidance.

In plain words
What is it for?
Use it when building pages for a café or bakery, including menus, ordering information, venue details, coffee and food sections, staff, and farms.
Why use it?
It gives a food-and-drink website a consistent, welcoming appearance and makes practical details such as the menu, hours, address, and ordering easy to present.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it when building pages for a café or bakery, including menus, ordering information, venue details, coffee and food sections, staff, and farms.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/aimeos/pagible/brew
Install

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.

Any agent
npx skills add aimeos/pagible --skill brew
Clone the repo
git clone --depth 1 https://github.com/aimeos/pagible

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for brew

README.md
[![agentmods](https://agentmods.dev/badge/skills/aimeos/pagible/brew/github.svg)](https://agentmods.dev/skills/aimeos/pagible/brew)
Your own site
<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.

agentmods 80×15 button for brew

Your own site · 80×15
<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>
Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 842 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 8d ago against content hash 10f86bac34c2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

themes/brew/SKILL.md · 46 lines

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 1280px maximum 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 figures layout for opening year, farms, fermentation hours or opening time, and in the badges layout 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: pricing elements 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: pricing elements with three items, the middle one highlighted with a badge.
  • Process: horizontal timelines for farm to cup, class afternoons or ordering.
  • Journal: blog pages 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 cafe config 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.

Read the full file on GitHub · 46 lines

Changes

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.

  1. 8d ago First seen · 46 lines · 33 tokens per session scan A 10f86bac34c2

Subscribe to this mod's changes

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.

Related

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.

buiphucminhtam/forgewright · 73 tokens

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"…

JPeetz/agent-skills · 117 tokens

strapi-cms

Customisable headless CMS with Strapi.

bidewio/better-openclaw · 13 tokens

api-design

Applies REST and GraphQL design principles to produce or review an API contract.

MarieLynneBlock/arcanum-artifex · 19 tokens

api-integration-architect

Design, implement, debug, and optimize API integrations with expert-level patterns for REST, GraphQL, webhooks, and authentication flows.

sickn33/agentic-awesome-skills · 33 tokens

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…

scalar/scalar · 68 tokens