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 medicalgit 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/medical)<a href="https://agentmods.dev/skills/aimeos/pagible/medical"><img src="https://agentmods.dev/badge/skills/aimeos/pagible/medical/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/medical"><img src="https://agentmods.dev/badge/skills/aimeos/pagible/medical.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.00034 | $0.00781 |
| Opus 5.5 | $0.00014 | $0.00312 |
| Sonnet 5.5 | $0.00007 | $0.00156 |
| Haiku 4.5 | $0.00003 | $0.00078 |
Grade A, and why
medical 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 9d 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.
Medical Theme Design System
Direction
Use a calm, clean layout that makes patients feel welcome and well informed before their first visit. Put treatments, the team, opening hours, insurance and self-pay prices, what to expect at an appointment and the way to book first, and explain instead of promising.
Foundations
- Use only the markup and classes supplied by
./theme/views/. - Use system fonts (humanist sans-serif fonts for headings) and the existing
--pico-*variables. - Keep page content within a
1280pxmaximum width. - Use a white header, navy (
#0F2D3A) for the footer and dark sections, teal (#0A7782) for links, buttons and heading markers, and mint (#8DD8C8) only for fills, badges and text on dark backgrounds, never for text on light backgrounds. - Use rounded corners, pill-shaped buttons, thin borders and soft shadows; dark sections show a soft dot pattern, the hero ends in a gentle curve and headings use plus markers.
Components
- Hero: a bright photo of a consultation or the practice as background with a short, reassuring headline, a mint tag line, a curved edge at the bottom and a "Book an appointment" action.
- Treatments: cards with a photo, a short text and a link to the treatment page; treatment pages name the responsible dentist, link a matching guide and answer cost and insurance questions. Include anxious patients and dental emergencies.
- Figures and badges: cards in the
figureslayout for years, team size, waiting time and reviews, and in thebadgeslayout with line icons for new patients, insurances, accessibility, languages and memberships. - Team: cards with portrait photos of the same ratio, the name as title and qualifications and focus as text; the team size matches the figures.
- Prices: a
pricingelement with typical prices for self-pay services, always with a note on cost plans. - First visit: a horizontal timeline from booking to the treatment plan.
- Patient guides:
blogpages below the guides page, each with an article, key figures, a vertical step timeline, questions and a call to action. - Appointment: a contact form with selects for the reason, new or existing patient, insurance and preferred time, plus a map with opening hours and directions.
- Patient info: what to bring, insurance and costs, emergencies and directions, followed by questions.
- Footer: opening hours with the emergency number, treatments, practice links including careers, imprint and privacy, and contact.
- Practice details: the
practiceconfig adds the medical business JSON-LD, the call button for phones, the top bar with telephone and emergency number and the booking button in the header.
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 707 B
- database/seeders/MedicalDemo.php 75 KB
- i18n/af.po 3.1 KB
- i18n/ar.po 3.4 KB
- i18n/az.po 3.2 KB
- i18n/bg.po 3.6 KB
- i18n/ca.po 3.1 KB
- i18n/cs.po 3.1 KB
- i18n/da.po 3.0 KB
- i18n/de.po 3.1 KB
- i18n/el.po 3.6 KB
- i18n/en.po 3.1 KB
- i18n/es.po 3.1 KB
- i18n/et.po 3.1 KB
- i18n/fa.po 3.5 KB
- i18n/fi.po 3.2 KB
- i18n/fr.po 3.1 KB
- i18n/he.po 3.4 KB
- i18n/hr.po 3.1 KB
- i18n/hu.po 3.1 KB
- i18n/id.po 3.1 KB
- i18n/it.po 3.1 KB
- i18n/ja.po 3.1 KB
- i18n/km.po 4.0 KB
- i18n/ko.po 3.1 KB
- i18n/lt.po 3.2 KB
- i18n/lv.po 3.1 KB
- i18n/messages.pot 2.5 KB
- i18n/nl.po 3.1 KB
- i18n/no.po 3.0 KB
- i18n/pl.po 3.1 KB
- i18n/pt-BR.po 3.2 KB
- i18n/pt.po 3.2 KB
- i18n/ro.po 3.1 KB
- i18n/ru.po 3.6 KB
- i18n/sk.po 3.1 KB
- i18n/sl.po 3.1 KB
- i18n/sr.po 3.6 KB
- i18n/sv.po 3.1 KB
- i18n/th.po 3.8 KB
- i18n/tr.po 3.1 KB
- i18n/uk.po 3.6 KB
- i18n/vi.po 3.2 KB
- i18n/zh-TW.po 3.0 KB
- i18n/zh.po 3.0 KB
- lang/af.json 150 B
- lang/ar.json 179 B
- lang/az.json 171 B
- lang/bg.json 211 B
- lang/ca.json 156 B
- lang/cs.json 157 B
- lang/da.json 147 B
- lang/de.json 169 B
- lang/el.json 217 B
- lang/en.json 157 B
- lang/es.json 157 B
- lang/et.json 166 B
- lang/fa.json 207 B
- lang/fi.json 158 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.
- 9d ago First seen · 47 lines · 34 tokens per session scan A db88ace13f4b
medical is a skill published in the GitHub repository aimeos/pagible (596 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 781 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.
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…