brand-guidelines

brand-guidelines is a skill for Claude Code from opensesh/DESIGN-OPS. It costs 42 tokens per session (1,076 once invoked), scanned A, original, Apache-2.0.

A guide for applying an organisation’s visual and writing standards to creative work, including colours, typography, identity and tone.

In plain words
What is it for?
Use it when creating branded content, checking work against brand rules, choosing design details or matching a brand’s writing style.
Why use it?
It helps keep designs and copy consistent instead of making brand decisions from scratch each time.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the design-ops plugin — 5 skills, 13 commands shipped together

Good fit Use it when creating branded content, checking work against brand rules, choosing design details or matching a brand’s writing style.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/opensesh/design-ops/brand-guidelines
Install

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.

Any agent
npx skills add opensesh/DESIGN-OPS --skill brand-guidelines
Clone the repo
git clone --depth 1 https://github.com/opensesh/DESIGN-OPS

Made for: Claude Code.

Or install design-ops, the plugin that ships this one along with the rest of its 5 skills, 13 commands.

Wrote 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.

agentmods badge for brand-guidelines

README.md
[![agentmods](https://agentmods.dev/badge/skills/opensesh/design-ops/brand-guidelines/github.svg)](https://agentmods.dev/skills/opensesh/design-ops/brand-guidelines)
Your own site
<a href="https://agentmods.dev/skills/opensesh/design-ops/brand-guidelines"><img src="https://agentmods.dev/badge/skills/opensesh/design-ops/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.

agentmods 80×15 button for brand-guidelines

Your own site · 80×15
<a href="https://agentmods.dev/skills/opensesh/design-ops/brand-guidelines"><img src="https://agentmods.dev/badge/skills/opensesh/design-ops/brand-guidelines.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,076 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00042 $0.01076
Opus 5 $0.00021 $0.00538
Sonnet 5 $0.00008 $0.00215
Haiku 4.5 $0.00004 $0.00108

Measured 10d ago against content hash 5ecf3a8019c5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

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 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.

skills/brand-guidelines/SKILL.md · 196 lines

How it starts

The opening of the file, as written. The whole thing — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Brand Guidelines

Apply consistent brand standards across all creative work, including visual identity, color usage, typography, and voice guidelines.

Purpose

Enable Claude to apply consistent brand standards across all creative work. This skill provides both a framework for brand consistency and a customizable template for organization-specific guidelines.

When to Activate

Use this skill when:

  • Creating any branded content or communications
  • Reviewing work for brand compliance
  • Making design decisions that affect brand consistency
  • Generating copy that needs to match brand voice
  • Working with Open Session colors (Aperol, Charcoal, Vanilla)

Brand Identity Framework

Brand Essence

One sentence that captures what the brand stands for.

Core Values

  1. [Value 1] - Brief description
  2. [Value 2] - Brief description
  3. [Value 3] - Brief description

Brand Personality

List 3-5 personality traits that define how the brand communicates.


Visual Identity

Color Palette

Primary Colors
Name Hex RGB Usage
Primary #000000 0, 0, 0 Headlines, CTAs
Secondary #000000 0, 0, 0 Supporting elements
Accent Colors
Name Hex RGB Usage
Accent 1 #000000 0, 0, 0 Highlights
Accent 2 #000000 0, 0, 0 Secondary highlights
Neutral Colors
Name Hex Usage
Dark #000000 Text, backgrounds
Light #FFFFFF Backgrounds, contrast

Typography

Primary Typeface
  • Name: [Font name]
  • Weights: [Available weights]
  • Usage: Headlines, key messaging
Secondary Typeface
  • Name: [Font name]
  • Weights: [Available weights]
  • Usage: Body text, UI elements
Type Scale
Element Size Weight Line Height
H1 [size] [weight] [line-height]
H2 [size] [weight] [line-height]
Body [size] [weight] [line-height]

Read the full file on GitHub · 196 lines

Changes

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.

  1. 10d ago First seen · 196 lines · 42 tokens per session scan A 5ecf3a8019c5

Subscribe to this mod's changes

brand-guidelines is a skill published in the GitHub repository opensesh/DESIGN-OPS (23 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 42 tokens to every session and 1,076 once invoked, about $0.0002 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.

Related

Other skills, from other repositories

system-pitch

Write a design system investment pitch with a business case and ROI framing. Trigger when someone says: pitch the design system, make the case for the system, sell this to leadership, justify the investment, business case for design systems, why should we invest in a design system, or anything about building an…

murphytrueman/design-system-ops · 72 tokens

stakeholder-brief

Write a one-page stakeholder brief translating design system health or status into business language. Trigger when someone says: stakeholder update, exec brief, leadership summary, status report for leadership, system status for non-designers, write a brief for the business, or anything about communicating design…

murphytrueman/design-system-ops · 73 tokens

token-audit

Audit a design system's token definitions for naming violations, missing semantic tiers, and structural debt. This audits how tokens are defined and organised, NOT how they are consumed in code. Trigger when someone says: audit my tokens, token naming review, are my tokens consistent, token health check, review my…

murphytrueman/design-system-ops · 93 tokens

accessibility-per-component

Run an accessibility audit on a specific design system component. Trigger when someone says: accessibility check, a11y audit, WCAG compliance, is this accessible, check accessibility, does this meet WCAG, screen reader support, keyboard navigation check, or anything about auditing the accessibility of a specific…

murphytrueman/design-system-ops · 65 tokens

ai-component-description

Generate AI-optimised text descriptions for components, formatted for Figma's MCP server and LLM consumption. This produces prose descriptions in a six-section format (purpose, props, anti-patterns, composition, accessibility, examples), NOT JSON schemas or structured data files. Trigger when someone says: write…

murphytrueman/design-system-ops · 132 tokens

context-engine-builder

Generate a context engine — seven structured blueprint files (UX, UI, content, accessibility, ethical, technical, business intelligence) that encode everything an AI agent needs to work with a design system. This produces YAML infrastructure in .ai/context-engine/, NOT a health score or quality assessment. Trigger…

murphytrueman/design-system-ops · 135 tokens