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 rampstackco/claude-skills --skill brand-identitygit clone --depth 1 https://github.com/rampstackco/claude-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/rampstackco/claude-skills/brand-identity)<a href="https://agentmods.dev/skills/rampstackco/claude-skills/brand-identity"><img src="https://agentmods.dev/badge/skills/rampstackco/claude-skills/brand-identity/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/rampstackco/claude-skills/brand-identity"><img src="https://agentmods.dev/badge/skills/rampstackco/claude-skills/brand-identity.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
- Socket pass
- Snyk pass
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 177 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00138 | $0.02393 |
| Opus 5 | $0.00069 | $0.01196 |
| Sonnet 5 | $0.00028 | $0.00479 |
| Haiku 4.5 | $0.00014 | $0.00239 |
Grade A, and why
brand-identity 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 10d 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 — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brand Identity
Design or evaluate the visual artifacts that express a brand: logo system, color, typography, imagery, iconography, and motion. Stack-agnostic. Tool-agnostic.
This skill assumes a brand direction is already approved (positioning, mood, name). If not, run brand-ideation first.
When to use
- Designing a logo system
- Defining a brand color palette
- Choosing brand typography
- Developing iconography or illustration style
- Defining imagery direction (photography, illustration)
- Establishing motion principles
- Auditing an existing identity for cohesion or gaps
When NOT to use
- Brand direction is not yet defined (use
brand-ideation) - Documenting a finished system (use
brand-style-guide) - Defining voice and tone (use
brand-voice) - Building UI components from an existing brand (use
design-standardsordesign-system)
Required inputs
- The brand name and approved positioning
- The mood direction (from ideation, or supplied as references)
- Audience and category context
- Application contexts (web, print, packaging, motion - whatever applies)
- Constraints (parent brand requirements, regulatory marks, accessibility minimums)
The framework: 5 elements
A complete identity has five elements. Each element should reinforce the others. Inconsistency between them is the most common identity failure.
1. Logo system
Most brands need not one logo but a system of marks for different contexts.
Components of a logo system:
- Primary mark. The main logo. Used wherever there is room.
- Wordmark. Just the typography, no symbol. Used in tight horizontal contexts.
- Symbol or glyph. Just the symbol, no type. Used in app icons, favicons, social avatars.
- Lockup variations. Horizontal, stacked, square - whichever apply.
- Monogram. The initial(s) styled as a mark. Optional but useful for small contexts.
Design principles:
- Legible at 16 pixels. Test the logo at favicon size. If it falls apart, redesign.
- Reproducible in single-color. If the logo only works in full color, it cannot be screen-printed, embroidered, or rendered in browser favicons.
- Distinctive silhouette. Squint at it. Can you still tell what it is? If it looks like every other logo in the category at silhouette, redesign.
- Construction grid. Every curve and angle is intentional. Document the construction.
What ships with it
2 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.
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.
- 10d ago First seen · 204 lines · 138 tokens per session scan A 91dc7f2acc3a
brand-identity is a skill published in the GitHub repository rampstackco/claude-skills (832 stars, last pushed 2d ago), licensed MIT. It adds 138 tokens to every session and 2,393 once invoked, about $0.0007 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
popular-web-designs
54 real design systems (Stripe, Linear, Vercel) as HTML/CSS.
visual-brand-extractor
Extract visual branding (colors, typography, layout patterns) from a client's website and generate a style preset compatible with the HTML slides skill and a brand config JSON for the content asset creator. Uses WebFetch to read pages and analyzes CSS/HTML to identify the color palette, font pairings, and aesthetic…
visual-qa
Runs rigorous visual QA across web, terminal, and paginated surfaces with screenshot evidence and a verdict. Use for any UI build or change, or when asked whether a page, component, or TUI looks right.
frontend
Builds, styles, and polishes web UI and UX. Use for any frontend, page, component, styling, layout, animation, or visual-quality task, or when asked to make an interface look or feel a certain way.
interaction-skill
Layer A interaction-mechanics reference anchored to the beui.dev catalog. Stacks on any style skill whenever work adds or changes motion or interaction — micro-interactions, animated components, transitions, gestures, hover/press/state feedback, loading/success/error morphs, 'make it feel alive'. Mandates reading the…
layout-skill
Layer A layout-mechanics reference. Stacks on any style skill when the screen is an app shell, dashboard, settings, list-detail, mail/inbox, or any layout with fixed regions plus a scrolling body — or when a layout breaks under long, empty, or unbroken content. Owns spatial structure and scroll ownership; owns zero…