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 agentmods add skills/aimeos/pagible/journalnpx skills add aimeos/pagible --skill journalgit 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/journal)<a href="https://agentmods.dev/skills/aimeos/pagible/journal"><img src="https://agentmods.dev/badge/skills/aimeos/pagible/journal.svg" alt="Measured on agentmods" 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.00024 | $0.00855 |
| Opus 5 | $0.00012 | $0.00428 |
| Sonnet 5 | $0.00005 | $0.00171 |
| Haiku 4.5 | $0.00002 | $0.00085 |
Grade A, and why
journal 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 6d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Journal Theme Design System
Mission
Build credible editorial pages that make dense reporting easy to scan without turning the interface into a dashboard.
Brand
Journal is sober, structured, and image-led. The page surround is warm gray (#F1EFEC), story modules are white, text is charcoal (#1F1E1C), and ochre (#8C620C) marks sections, actions, and active states. It uses Pico CSS and the existing markup in theme/views/.
Style Foundations
- Typography: Georgia or the nearest system serif for masthead and headlines; Arial/Helvetica/system sans-serif for navigation, metadata, controls, and body UI
- Headline rhythm: compact line height, strong weight, no centered marketing copy except the masthead
- Surfaces: consecutive content elements form one white editorial surface; warm-gray vertical gaps separate heroes and the outer content frame
- Geometry:
--pico-border-radius: 0; cards, dialogs, fields, and buttons stay square - Accent: ochre is reserved for categories, primary actions, focus, and active navigation
- Images: editorial crops use
16 / 10, article leads use16 / 9, and hero media fills its section without distortion - Maximum width: 1156px shared page frame, with narrower article and prose measures where readability requires them
Component Rules
- Header: center the masthead above a separate category rail on desktop; collapse to one accessible menu below 992px
- Hero: place the first content layer over the section image or slideshow and use a restrained dark overlay for legibility
- Story grids: present blog entries as four equal editorial cards on desktop, two on tablets, and one on phones
- Cards: use a bottom rule instead of rounded containers or shadows; change the rule to ochre on hover
- Articles: keep introductions and body copy on a narrow measure, while cover images may use the full content width
- Buttons: uppercase sans-serif labels, square borders, ochre primary action, white secondary action
- Footer: use sectioned link columns, a strong bottom rule, and the same masthead identity as the header
What ships with it
27 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 684 B
- database/seeders/JournalDemo.php 44 KB
- LICENSE 1.0 KB
- public/article.css 472 B
- public/cards.css 1.8 KB
- public/cms-lazy.css 5.9 KB
- public/cms.css 13 KB
- public/contact.css 1.7 KB
- public/hero.css 2.6 KB
- public/image-text.css 1.4 KB
- public/image.css 430 B
- public/layout-blog.css 653 B
- public/layout-docs.css 2.6 KB
- public/layout-page.css 957 B
- public/list.css 2.2 KB
- public/pricing.css 5.2 KB
- public/questions.css 1.0 KB
- public/slideshow.css 11 KB
- public/table.css 1.6 KB
- public/testimonial.css 1.4 KB
- public/toc.css 713 B
- public/video.css 381 B
- README.md 2.2 KB
- schema.json 3.6 KB
- src/JournalServiceProvider.php 471 B
- views/layouts/main.blade.php 12 KB
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.
- 6d ago First seen · 71 lines · 24 tokens per session scan A d4e2a4a5e292
journal is a skill published in the GitHub repository aimeos/pagible (585 stars, last pushed yesterday), licensed MIT. It adds 24 tokens to every session and 855 once invoked, about $0.0001 per session on Opus 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-08-30.
Other skills, from other repositories
ui4-review
Review UI4 CSS migrations for proper token usage. Checks that CSS variables are used instead of hardcoded values.
strapi-cms
Customisable headless CMS with Strapi.
Shade tokens, not hex
Use Shade semantic tokens (bg-background, text-foreground, border-border-default, bg-surface-elevated) — never hex, hsl(), or bg-gray-200-style raw palette utilities for UI chrome. Trigger when editing TSX/CSS in Shade-consuming apps.
ui4
Manually invoked skill for reskinning Payload UI components. Requires Figma URL. Usage: /ui4.
payload
Use when working with Payload projects (payload.config.ts, collections, fields, hooks, access control, Payload API). Use when debugging validation errors, security issues, relationship queries, transactions, or hook behavior.
Shade dropdown surface contract
DropdownMenu, Select, and Popover share one visual recipe (bg-surface-elevated-2 + border-border/60 dark:border-border/30 + shadow-md). Change them together. Trigger when editing any of those three Shade files.