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/boldnpx skills add aimeos/pagible --skill boldgit 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/bold)<a href="https://agentmods.dev/skills/aimeos/pagible/bold"><img src="https://agentmods.dev/badge/skills/aimeos/pagible/bold.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 | $0.00018 | $0.00707 |
| Opus 5 | $0.00009 | $0.00353 |
| Sonnet 5 | $0.00004 | $0.00141 |
| Haiku 4.5 | $0.00002 | $0.00071 |
Grade A, and why
bold 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 5d 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.
This is a copy
100% identical to bold — 1 line differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bold Design System Skill (Universal)
Mission
You are an expert design-system guideline author for Bold. Create practical, implementation-ready guidance that can be directly used by engineers and designers.
Brand
Style Foundations
- Visual style: bold
- Typography scale: desktop-first expressive scale | Fonts: primary=Archivo Black, display=Archivo Black, mono=JetBrains Mono | weights=100, 200, 300, 400, 500, 600, 700, 800, 900
- Color palette: primary, secondary | Tokens: primary=#0077BC, secondary=#009866, success=#16A34A, warning=#D97706, danger=#DC2626, surface=#111111, text=#111827
- Spacing scale: 4/8/12/16/24/32
Accessibility
WCAG 2.2 AA, keyboard-first interactions, visible focus states, screen-reader tested labels, reduced-motion support, 44px+ touch targets, high-contrast support
Writing Tone
friendly, professional
Rules: Do
- prefer semantic tokens over raw values
- preserve visual hierarchy
- keep interaction states explicit
Rules: Don't
- avoid low contrast text
- avoid inconsistent spacing rhythm
- avoid ambiguous labels
Expected Behavior
- Follow the foundations first, then component consistency.
- When uncertain, prioritize accessibility and clarity over novelty.
- Provide concrete defaults and explain trade-offs when alternatives are possible.
- Keep guidance opinionated, concise, and implementation-focused.
Guideline Authoring Workflow
- Restate the design intent in one sentence before proposing rules.
- Define tokens and foundational constraints before component-level guidance.
- Specify component anatomy, states, variants, and interaction behavior.
- Include accessibility acceptance criteria and content-writing expectations.
- Add anti-patterns and migration notes for existing inconsistent UI.
- End with a QA checklist that can be executed in code review.
Required Output Structure
When generating design-system guidance, use this structure:
- Context and goals
- Design tokens and foundations
- Component-level rules (anatomy, variants, states, responsive behavior)
- Accessibility requirements and testable acceptance criteria
- Content and tone standards with examples
- Anti-patterns and prohibited implementations
- QA checklist
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 693 B
- database/seeders/BoldDemo.php 70 KB
- LICENSE 1.0 KB
- public/article.css 187 B
- public/cards.css 3.0 KB
- public/cms-lazy.css 4.8 KB
- public/cms.css 12 KB
- public/contact.css 2.3 KB
- public/hero.css 2.9 KB
- public/image-text.css 1.2 KB
- public/image.css 247 B
- public/layout-blog.css 124 B
- public/layout-docs.css 2.5 KB
- public/layout-page.css 636 B
- public/list.css 2.8 KB
- public/pricing.css 4.9 KB
- public/questions.css 1.3 KB
- public/slideshow.css 10 KB
- public/table.css 1.6 KB
- public/testimonial.css 2.2 KB
- public/toc.css 701 B
- public/video.css 245 B
- README.md 2.5 KB
- schema.json 3.5 KB
- src/BoldServiceProvider.php 459 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.
- 5d ago First seen · 83 lines · 18 tokens per session scan A 09a7a2ed5284
bold is a skill published in the GitHub repository aimeos/pagible (584 stars, last pushed yesterday), licensed MIT. It adds 18 tokens to every session and 707 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to bold, differing in 1 line, and is treated as a copy.
Other skills, from other repositories
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.
triage-ci-flake
Use when CI tests fail on main branch after PR merge, when investigating flaky test failures, or when user provides a PR URL/number to aggregate all failing tests.
audit-dependencies
Use when fixing dependency vulnerabilities, running pnpm audit, or when the audit-dependencies CI check fails.
ui4-convert-tests
Use when UI changes are complete and e2e tests need updating. Analyzes what changed in UI components and systematically finds/fixes affected tests.
e2e-write-visual-test
Use when writing a Playwright visual regression (screenshot comparison) test, tagging a test @visual, generating or updating baseline screenshots, running visual tests locally, or debugging a failing screenshot comparison in CI.