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 opensesh/DESIGN-OPS --skill brand-guidelinesgit clone --depth 1 https://github.com/opensesh/DESIGN-OPSWrote 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/opensesh/design-ops/brand-guidelines)<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.
<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>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.00042 | $0.01076 |
| Opus 5.5 | $0.00017 | $0.00430 |
| Sonnet 5.5 | $0.00008 | $0.00215 |
| Haiku 4.5 | $0.00004 | $0.00108 |
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 2mo 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 — 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
- [Value 1] - Brief description
- [Value 2] - Brief description
- [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] |
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.
- 2mo ago First seen · 196 lines · 42 tokens per session scan A 5ecf3a8019c5
brand-guidelines is a skill published in the GitHub repository opensesh/DESIGN-OPS (23 stars, last pushed 23d 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.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
theme-audit
Audit theme parity: tokens missing or unchanged per theme, component tokens bypassing semantics, contrast within each theme, resolver contexts, theme-switch regressions. Triggers: dark mode audit, theme coverage, brand variant parity. For general token structure use token-audit.
token-audit
Audit how design tokens are defined: tiers, naming, alias chains, raw values, orphans, DTCG readiness. Triggers: audit my tokens, token architecture review, token health check. Not for code consuming tokens (token-compliance), theme parity (theme-audit) or Figma variables (figma-variable-audit).
accessibility-per-component
Audit one design system component's accessibility against WCAG 2.2 AA: keyboard, screen reader, contrast, focus, ARIA, target size. Trigger: a11y audit, is this accessible, WCAG check, screen reader support, keyboard navigation check. Not for page- or product-wide audits.
ai-component-description
Write a six-section prose description (purpose, props, anti-patterns, composition, accessibility, examples) for a Figma component's description field so LLMs read it via MCP. Triggers: describe this component for AI, Figma MCP description. JSON metadata files: use metadata-schema-generator.
component-decision-tree
Write "choosing between" pages (docs/choosing/) that route an intent to the right component via narrowing questions; YAML trees on request. Triggers: which component should I use, choose between X and Y, dialog vs drawer, selection guide. One chosen component: usage-guidelines.
figma-variable-audit
Audit Figma variable collections: tier mapping, naming, alias chains, modes, orphans; can fix in place with Figma Console MCP. Triggers: audit my Figma variables, review variable collections, Figma variable health. For token files in code use token-audit.