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 manu14357/zskills --skill brand-guidelinesgit clone --depth 1 https://github.com/manu14357/zskillsWrote 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/manu14357/zskills/brand-guidelines)<a href="https://agentmods.dev/skills/manu14357/zskills/brand-guidelines"><img src="https://agentmods.dev/badge/skills/manu14357/zskills/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/manu14357/zskills/brand-guidelines"><img src="https://agentmods.dev/badge/skills/manu14357/zskills/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.00036 | $0.00968 |
| Opus 5 | $0.00018 | $0.00484 |
| Sonnet 5 | $0.00007 | $0.00194 |
| Haiku 4.5 | $0.00004 | $0.00097 |
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 11d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenAI Brand Styling
Use This Skill When
- Applying OpenAI's brand identity to presentations or artifacts
- Ensuring visual consistency with Codex/OpenAI design standards
- Selecting colors or typography that match OpenAI branding
- Styling UI components or documents with corporate identity
- Creating branded materials that need professional visual identity
When NOT to Use
- Non-OpenAI projects or different brand guidelines
- When brand compliance is not required
- For generic design without specific brand standards
- When custom color schemes are explicitly requested
Context: Brand Implementation
Undeveloped: No brand standards applied; generic styling only.
Target: OpenAI colors, typography, and design standards consistently applied to all visual elements.
Optimized: Brand guidelines automatically enforced across all artifacts with smart fallbacks and accessibility considerations.
Core Principle
Strong visual branding creates trust and recognition. OpenAI's palette and typography should be applied consistently to maintain a professional, cohesive identity across all materials.
Instructions
Step 1: Understand OpenAI Brand Palette
Main Colors:
- Charcoal
#0E0F12- Primary text, dark backgrounds - Slate
#202123- Surface backgrounds - Mist
#F5F7FA- Light backgrounds, text on dark - Steel
#9EA1AA- Secondary elements, dividers
Accent Colors:
- OpenAI Green
#10A37F- Primary accent - Azure
#2B8FFF- Secondary accent - Graphite
#40434A- Neutral accent for icons/strokes
Step 2: Apply Typography Standards
Font Stack (with fallbacks):
- Headings (24pt+): Inter Semibold/Bold → Arial
- Body Text: Inter Regular → Arial
- Code/Monospace: IBM Plex Mono → Menlo/monospace
Rules:
- Headings: 24pt or larger
- Body text: Regular weight
- Code snippets: Always monospace
- Automatic fallback if fonts unavailable
Step 3: Select Colors by Context
| Element | Color | Use Case |
|---|---|---|
| Primary Text | Charcoal | Dark backgrounds, main content |
| Background | Slate or Mist | Based on contrast needs |
| Accent (Primary) | OpenAI Green | Call-to-action, highlights |
| Accent (Secondary) | Azure | Secondary actions, links |
| Dividers/Icons | Steel or Graphite | Subtle separation, neutral icons |
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.
- 11d ago First seen · 123 lines · 36 tokens per session scan A 53dcc42992c5
brand-guidelines is a skill published in the GitHub repository manu14357/zskills (16 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 968 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…