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 ErikaAX08/erikas-skills --skill brand-guidelinesgit clone --depth 1 https://github.com/ErikaAX08/erikas-skillsWrote 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/erikaax08/erikas-skills/brand-guidelines)<a href="https://agentmods.dev/skills/erikaax08/erikas-skills/brand-guidelines"><img src="https://agentmods.dev/badge/skills/erikaax08/erikas-skills/brand-guidelines/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/erikaax08/erikas-skills/brand-guidelines"><img src="https://agentmods.dev/badge/skills/erikaax08/erikas-skills/brand-guidelines.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.00046 | $0.04741 |
| Opus 5.5 | $0.00018 | $0.01896 |
| Sonnet 5.5 | $0.00009 | $0.00948 |
| Haiku 4.5 | $0.00005 | $0.00474 |
Grade A, and why
brand-guidelines 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 today.
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 — 519 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brand Styling Skill
Overview
This skill applies brand-specific colors and typography to any artifact that may benefit from having a consistent visual identity. It is designed to work with any brand palette, not a single predefined one.
Keywords: branding, corporate identity, visual identity, post-processing, styling, brand colors, typography, visual formatting, visual design, color palette, design system
Critical Rule: Prefer UI Library Components Over New Ones
Whenever a new component is needed, first check whether the project is using a UI
library (e.g.: shadcn/ui, Material UI, Chakra UI, Radix, Ant Design, PrimeVue,
Vuetify, etc.). Look for telltale signs such as components.json, a components/ui/
folder, or the library listed in package.json.
- If a UI library is in use, use its components exclusively instead of building new ones from scratch. Compose, extend, and theme the library's components rather than reinventing buttons, inputs, dialogs, tables, etc.
- Only create a brand-new custom component when the required UI does not exist in the library, and even then build it on top of the library's primitives and tokens when possible.
- Apply the brand palette and typography through the library's theming mechanism (CSS variables, theme provider, tokens) so styling stays consistent with the library.
- Never duplicate a component the library already provides.
Critical Rule: Always Ask for the Color Palette First
Before applying any styling, this skill MUST ask the user for their specific brand palette and typography preferences.
Never assume or use a default palette without explicit confirmation. If the user does not provide one, prompt them with the following questions.
Required Information to Collect
When this skill is invoked, gather the following information from the user:
1. Color Palette
Ask the user to provide their brand colors in the following categories:
Please provide your brand color palette:
**Main Colors:**
- Dark (primary text and dark backgrounds): [color/hex]
- Light (light backgrounds and text on dark): [color/hex]
- Mid Gray (secondary elements): [color/hex]
- Light Gray (subtle backgrounds): [color/hex]
**Accent Colors:**
- Primary accent: [color/hex]
- Secondary accent: [color/hex]
- Tertiary accent: [color/hex]
**Optional Extended Palette:**
- Success/Positive: [color/hex]
- Warning/Caution: [color/hex]
- Error/Negative: [color/hex]
- Info/Neutral: [color/hex]
What ships with it
1 file 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.
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.
- today First seen · 519 lines · 46 tokens per session scan A fde2fb6112f5
brand-guidelines is a skill published in the GitHub repository ErikaAX08/erikas-skills (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 46 tokens to every session and 4,741 once invoked, about $0.0002 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-26.
Other skills, from other repositories
tailwind-design-system
Build scalable design systems with Tailwind CSS v4, design tokens, component libraries, and responsive patterns. Use when creating component libraries, implementing design systems, or standardizing UI patterns.
scrollcraft-layout
Turn a static site into a premium, multi-layered, scroll-driven experience (the "ScrollCraft" approach from Nate Herk's Claude design-skill video, adapted to Anton's no-npm static sites). Use when Anton asks for "multi-layered layout", "layers when you scroll", "interactive scrolling", "make it gorgeous / premium"…
industrial-brutalist-ui
Raw mechanical interfaces fusing Swiss typographic print with military terminal aesthetics. Rigid grids, extreme type scale contrast, utilitarian color, analog degradation effects. For data-heavy dashboards, portfolios, or editorial sites that need to feel like declassified blueprints.
impeccable-design
Visual design quality enforcement. 50 deterministic anti-pattern rules preventing AI design slop. Bans generic fonts, pure colors, nested cards, dated animations. Adapted for Tailwind CSS v4, shadcn/ui, and Framer Motion stacks.
minimalist-ui
Clean editorial-style interfaces. Warm monochrome palette, typographic contrast, flat bento grids, muted pastels. No gradients, no heavy shadows.
redesign-existing-projects
Upgrades existing websites and apps to premium quality. Audits current design, identifies generic AI patterns, and applies high-end design standards without breaking functionality. Works with any CSS framework or vanilla CSS.