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 foliogit 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/folio)<a href="https://agentmods.dev/skills/aimeos/pagible/folio"><img src="https://agentmods.dev/badge/skills/aimeos/pagible/folio/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/folio"><img src="https://agentmods.dev/badge/skills/aimeos/pagible/folio.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.00063 | $0.00981 |
| Opus 5.5 | $0.00025 | $0.00392 |
| Sonnet 5.5 | $0.00013 | $0.00196 |
| Haiku 4.5 | $0.00006 | $0.00098 |
Grade A, and why
folio 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 3d 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Folio Theme Design System
Direction
Build a personal website like the best developer blogs and portfolios (leerob.com, overreacted.io, brittanychiang.com, antfu.me): one person, one voice, and the writing comes first. The site should feel like a well-kept notebook, quiet and fast, with nothing that competes with the text. Show what the person built and learned with concrete numbers and code. Use no stock photos of people, no marketing claims and no decorative effects.
Foundations
- Use only the markup and classes supplied by
./theme/views/and the theme'sarticle,blog,code,text,bloglayout andmainviews. - Use the system sans-serif, serif and monospace fonts and the existing
--pico-*variables. - Use warm neutrals (
#2B2924,#6B665E,#E4E0D9,#FBFAF8) and green (#1F7A4D,#4FBF87in dark mode) only for links and the first button; code blocks always stay dark. - Support light and dark mode; never place fixed light colors on themeable backgrounds.
- Use
0.5remcorners and thin borders instead of shadows.
Structure
- Home (
page): aherowith the avatar as image, the role as subtitle, a one-sentence introduction and two buttons, ablogelement with thelistlayout and "Recent writing" as title, two-column projectcardsand actafor contact. - Writing (
page): a short note on what you write about and abloglist of all posts with this page as parent page. - Posts (
blog) below Writing, newest first in the tree. Each starts with anarticleelement (title, a two-sentence lead and a cover image), followed bytext, level-2headingandcodeelements. - About, Projects, Uses and Now pages (
page) start with a level-1heading. About contains averticaltimeline of jobs, Uses lists tools by category and Now says what you're doing this month with the date of the last update. - Fill the
folio::profileconfig on the home page: name, job title, company, location, a square photo, a one-sentence bio, the e-mail address and profile links.
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 809 B
- database/seeders/FolioDemo.php 30 KB
- i18n/af.po 2.6 KB
- i18n/ar.po 2.8 KB
- i18n/az.po 2.7 KB
- i18n/bg.po 2.9 KB
- i18n/ca.po 2.7 KB
- i18n/cs.po 2.5 KB
- i18n/da.po 2.5 KB
- i18n/de.po 2.5 KB
- i18n/el.po 3.0 KB
- i18n/en.po 2.5 KB
- i18n/es.po 2.5 KB
- i18n/et.po 2.5 KB
- i18n/fa.po 3.1 KB
- i18n/fi.po 2.5 KB
- i18n/fr.po 2.6 KB
- i18n/he.po 2.8 KB
- i18n/hr.po 2.6 KB
- i18n/hu.po 2.5 KB
- i18n/id.po 2.5 KB
- i18n/it.po 2.5 KB
- i18n/ja.po 2.7 KB
- i18n/km.po 3.5 KB
- i18n/ko.po 2.5 KB
- i18n/lt.po 2.6 KB
- i18n/lv.po 2.5 KB
- i18n/messages.pot 1.9 KB
- i18n/nl.po 2.5 KB
- i18n/no.po 2.5 KB
- i18n/pl.po 2.5 KB
- i18n/pt-BR.po 2.7 KB
- i18n/pt.po 2.5 KB
- i18n/ro.po 2.6 KB
- i18n/ru.po 3.0 KB
- i18n/sk.po 2.5 KB
- i18n/sl.po 2.5 KB
- i18n/sr.po 3.0 KB
- i18n/sv.po 2.5 KB
- i18n/th.po 3.3 KB
- i18n/tr.po 2.6 KB
- i18n/uk.po 3.0 KB
- i18n/vi.po 2.7 KB
- i18n/zh-TW.po 2.6 KB
- i18n/zh.po 2.5 KB
- lang/af.json 577 B
- lang/ar.json 711 B
- lang/az.json 611 B
- lang/bg.json 755 B
- lang/ca.json 592 B
- lang/cs.json 605 B
- lang/da.json 573 B
- lang/de.json 594 B
- lang/el.json 838 B
- lang/en.json 553 B
- lang/es.json 597 B
- lang/et.json 582 B
- lang/fa.json 658 B
- lang/fi.json 608 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.
- 3d ago First seen · 50 lines · 63 tokens per session scan A fc3c6892afaf
folio is a skill published in the GitHub repository aimeos/pagible (596 stars, last pushed today), licensed MIT. It adds 63 tokens to every session and 981 once invoked, about $0.0003 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-15.
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…