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 flowgit 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/flow)<a href="https://agentmods.dev/skills/aimeos/pagible/flow"><img src="https://agentmods.dev/badge/skills/aimeos/pagible/flow/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/flow"><img src="https://agentmods.dev/badge/skills/aimeos/pagible/flow.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.00032 | $0.00652 |
| Opus 5.5 | $0.00013 | $0.00261 |
| Sonnet 5.5 | $0.00006 | $0.00130 |
| Haiku 4.5 | $0.00003 | $0.00065 |
Grade A, and why
flow 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flow Theme Design System
Direction
Use a clean, calm layout that makes homeowners and landlords trust the company with their heating, water and gas. Put services, fixed prices, certifications, the emergency number and the way to a quote first, and show real numbers instead of slogans.
Foundations
- Use only the markup and classes supplied by
./theme/views/. - Use system fonts (rounded system fonts for headings) and the existing
--pico-*variables. - Keep page content within a
1280pxmaximum width. - Use deep petrol (
#0A2B3B) for header, footer and dark sections, water blue (#0B7A9E) for links, buttons and markers, and copper (#E07B39) only for fills, badges and the emergency bar, never for text on light backgrounds. - Use rounded corners, thin borders and soft shadows; keep dark sections plain and headings without decorative markers.
Components
- Emergency bar: the emergency number from the
businessconfig at the top of every page. - Header: the office phone from the
businessconfig next to the last menu item, which is shown as a copper quote button (link it to the contact page). - Hero: a plumber, heat pump or finished bathroom photo as background, kept visible on the right, with a short headline, a copper tag line and a "Get a fixed price" action.
- Services: cards with a photo, a short text and a linked title; the whole card is clickable.
- Figures and badges: cards in the
figureslayout for years, jobs, response time and reviews, placed directly after the hero as a floating strip, and in thebadgeslayout for certifications, shown as tiles with a shield icon when they have no logo. - Prices: a
pricingelement with one-time fixed prices for typical jobs. - Process: a horizontal timeline from the first contact to the handover.
- Projects:
blogpages below the projects page, each with an article, key figures, a before/after comparison of same-sized photos, a vertical step timeline and a slideshow. - Contact: a contact form with a job type select, postcode and attachments for photos.
- Business details: the
businessconfig adds the local business JSON-LD, the emergency contact point and the call button 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/FlowDemo.php 51 KB
- i18n/af.po 609 B
- i18n/ar.po 684 B
- i18n/az.po 626 B
- i18n/bg.po 697 B
- i18n/ca.po 629 B
- i18n/cs.po 625 B
- i18n/da.po 620 B
- i18n/de.po 622 B
- i18n/el.po 714 B
- i18n/en.po 616 B
- i18n/es.po 624 B
- i18n/et.po 622 B
- i18n/fa.po 714 B
- i18n/fi.po 617 B
- i18n/fr.po 626 B
- i18n/he.po 647 B
- i18n/hr.po 616 B
- i18n/hu.po 648 B
- i18n/id.po 612 B
- i18n/it.po 618 B
- i18n/ja.po 631 B
- i18n/km.po 716 B
- i18n/ko.po 631 B
- i18n/lt.po 614 B
- i18n/lv.po 630 B
- i18n/messages.pot 520 B
- i18n/nl.po 615 B
- i18n/no.po 619 B
- i18n/pl.po 605 B
- i18n/pt-BR.po 667 B
- i18n/pt.po 632 B
- i18n/ro.po 624 B
- i18n/ru.po 716 B
- i18n/sk.po 625 B
- i18n/sl.po 618 B
- i18n/sr.po 671 B
- i18n/sv.po 620 B
- i18n/th.po 764 B
- i18n/tr.po 614 B
- i18n/uk.po 698 B
- i18n/vi.po 655 B
- i18n/zh-TW.po 603 B
- i18n/zh.po 599 B
- lang/af.json 107 B
- lang/ar.json 150 B
- lang/az.json 120 B
- lang/bg.json 160 B
- lang/ca.json 119 B
- lang/cs.json 116 B
- lang/da.json 112 B
- lang/de.json 116 B
- lang/el.json 178 B
- lang/en.json 115 B
- lang/es.json 121 B
- lang/et.json 125 B
- lang/fa.json 169 B
- lang/fi.json 119 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 Changed · +1 lines · -3 tokens per session 5a1372ac954e
- 9d ago First seen · 44 lines · 35 tokens per session scan A 09e6b576e9d5
flow is a skill published in the GitHub repository aimeos/pagible (596 stars, last pushed today), licensed MIT. It adds 32 tokens to every session and 652 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-09.
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.
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…