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 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/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/bold"><img src="https://agentmods.dev/badge/skills/aimeos/pagible/bold.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.00018 | $0.00707 |
| Opus 5.5 | $0.00007 | $0.00283 |
| Sonnet 5.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 1mo 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
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 693 B
- database/seeders/BoldDemo.php 62 KB
- i18n/af.po 159 B
- i18n/ar.po 167 B
- i18n/az.po 161 B
- i18n/bg.po 163 B
- i18n/ca.po 159 B
- i18n/cs.po 161 B
- i18n/da.po 159 B
- i18n/de.po 161 B
- i18n/el.po 163 B
- i18n/en.po 160 B
- i18n/es.po 159 B
- i18n/et.po 160 B
- i18n/fa.po 165 B
- i18n/fi.po 160 B
- i18n/fr.po 161 B
- i18n/he.po 172 B
- i18n/hr.po 159 B
- i18n/hu.po 160 B
- i18n/id.po 159 B
- i18n/it.po 159 B
- i18n/ja.po 164 B
- i18n/km.po 182 B
- i18n/ko.po 161 B
- i18n/lt.po 159 B
- i18n/lv.po 160 B
- i18n/messages.pot 138 B
- i18n/nl.po 160 B
- i18n/no.po 159 B
- i18n/pl.po 160 B
- i18n/pt-BR.po 162 B
- i18n/pt.po 159 B
- i18n/ro.po 160 B
- i18n/ru.po 184 B
- i18n/sk.po 160 B
- i18n/sl.po 159 B
- i18n/sr.po 163 B
- i18n/sv.po 159 B
- i18n/th.po 164 B
- i18n/tr.po 159 B
- i18n/uk.po 184 B
- i18n/vi.po 166 B
- i18n/zh-TW.po 164 B
- i18n/zh.po 161 B
- LICENSE 1.0 KB
- public/article.css 187 B
- public/before-after.css 2.1 KB
- public/cards.css 5.0 KB
- public/cms-lazy.css 4.8 KB
- public/cms.css 12 KB
- public/contact.css 2.3 KB
- public/cta.css 1018 B
- public/hero.css 2.9 KB
- public/i18n/af.json 36 B
- public/i18n/ar.json 44 B
- public/i18n/az.json 38 B
- public/i18n/bg.json 40 B
- public/i18n/ca.json 36 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.
- 1mo ago First seen · 83 lines · 18 tokens per session scan A 09a7a2ed5284
bold is a skill published in the GitHub repository aimeos/pagible (598 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.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
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.
api-testing-patterns
Comprehensive API testing patterns including contract testing, REST/GraphQL testing, and integration testing. Use when testing APIs or designing API test strategies.