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 nimadorostkar/Claude-Skills-collection --skill brand-guidelinesgit clone --depth 1 https://github.com/nimadorostkar/Claude-Skills-collectionWrote 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/nimadorostkar/claude-skills-collection/brand-guidelines)<a href="https://agentmods.dev/skills/nimadorostkar/claude-skills-collection/brand-guidelines"><img src="https://agentmods.dev/badge/skills/nimadorostkar/claude-skills-collection/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/nimadorostkar/claude-skills-collection/brand-guidelines"><img src="https://agentmods.dev/badge/skills/nimadorostkar/claude-skills-collection/brand-guidelines.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00038 | $0.01206 |
| Opus 5 | $0.00019 | $0.00603 |
| Sonnet 5 | $0.00008 | $0.00241 |
| Haiku 4.5 | $0.00004 | $0.00121 |
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 13d 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brand Guidelines
Purpose
Apply a brand consistently, and document it well enough that someone else can too. A brand that exists only in one designer's judgment is not a brand; it is a taste.
When to Use
- Applying an existing brand to new material.
- Documenting a brand that has never been written down.
- Auditing material for brand consistency.
- Extracting a system from a set of existing assets.
Capabilities
- Extracting colour, type, spacing, and voice from existing assets.
- Documenting a usable brand system.
- Applying a brand across media.
- Auditing for drift.
Inputs
- Existing brand assets, or a brand guideline document.
- The material to be produced or audited.
- The medium and its constraints.
Outputs
- A documented system: colour, type, spacing, imagery, voice.
- Material that is on-brand and can be verified as such.
- A list of the places the brand has drifted.
Workflow
- Extract before inventing — If a brand exists in assets but not in a document, derive it: sample the colours, identify the typefaces, measure the spacing, read the copy for voice. What is consistent across the assets is the brand; what varies is drift.
- Document the decisions, not just the values — "Primary blue #2563EB, used for actions and links only. Never for large fills." The constraint is the useful part.
- Cover the cases people get wrong — Minimum logo size, clear space, what to do on a dark background, what happens when the brand colour fails contrast.
- Document the voice — It is half the brand and it is nearly always omitted. Give examples of on-brand and off-brand copy.
- Apply, then audit — Check the output against the system rather than against instinct.
Best Practices
- A brand guideline without a "do not" section is not usable. The prohibitions are what prevent drift.
- Colour is where drift starts. Two similar blues in circulation becomes five within a year.
- The brand's primary colour frequently fails accessibility contrast for text. Document what to use instead, before someone ships an unreadable button.
- Voice examples do more than adjectives. "Confident, not arrogant" means nothing; a before-and-after pair of sentences means something.
- Logo misuse — stretching, recolouring, placing on a busy photograph — is universal and is prevented only by showing the wrong version explicitly.
- A brand that cannot survive being applied by a non-designer is not documented well enough.
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.
- 13d ago First seen · 109 lines · 38 tokens per session scan A 35e030a48c2c
brand-guidelines is a skill published in the GitHub repository nimadorostkar/Claude-Skills-collection (26 stars, last pushed 25d ago), licensed MIT. It adds 38 tokens to every session and 1,206 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
accessibility
Audit and improve web accessibility following WCAG 2.2 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible".
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use when the user asks to build landing pages, websites, dashboards, web components, or any frontend UI. Generates creative, polished code that avoids generic AI aesthetics.
prototype
Build a self-contained local prototype at .turbo/prototypes/ .html, drive it, and hand it to the user to settle unknowns that prose cannot answer. Use when the user asks to "prototype this", "build a prototype", "mock this up", "show me what it would look like", "let me try the interaction first", or when a decision…
user-experience
Apply a UX lens to a user-facing change: whether it serves the user's real goal and whether the path through it holds together, using the Understanding, Bridging, and Flowing contexts. Use when scoping, planning, or assessing any change that affects what a user sees or does. Loaded as a lens during planning and…
slop-eval
Objectively evaluate a UI/web design against the pols.dev anti-slop design law: detect catalogued slop tells with cited evidence, score 8 weighted axes (color, type, components, layout, motion, execution, signature, cohesion), and emit a Slop Report with a 0–100 Slop Index and grade. Use when the user asks to…
design-md-validator
Validate DESIGN.md files against the official Google specification using the @google/design.md CLI linter. Works with local files. Use when the user wants to lint a DESIGN.md, check spec compliance, find broken token references, verify WCAG contrast ratios, diff two versions, export tokens to Tailwind or DTCG format…