What is add-branding?

A skill for changing an application shell’s branding through configuration files, including themes, colors, navigation, logos, icons, and fonts.

It helps customize the app name, startup destination, chat mode, navigation, theme, logos, icons, fonts, and selected authentication settings.

It helps keep visual and shell changes organized in declarative settings rather than scattering them through application code.

How BlocUnited-LLC/mozaiks configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to BlocUnited-LLC/mozaiks. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/BlocUnited-LLC/mozaiks/main/.agents/skills/add-branding/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/BlocUnited-LLC/mozaiks

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/blocunited-llc/mozaiks/add-branding/github.svg)](https://agentmods.dev/skills/blocunited-llc/mozaiks/add-branding)

Your own site

<a href="https://agentmods.dev/skills/blocunited-llc/mozaiks/add-branding"><img src="https://agentmods.dev/badge/skills/blocunited-llc/mozaiks/add-branding/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/blocunited-llc/mozaiks/add-branding"><img src="https://agentmods.dev/badge/skills/blocunited-llc/mozaiks/add-branding.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,174 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. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.

Model	Per session	Once invoked
Fable 5.1	$0.00031	$0.01174
Opus 5.5	$0.00012	$0.00470
Sonnet 5.5	$0.00006	$0.00235
Haiku 4.5	$0.00003	$0.00117

Measured 26d ago against content hash 3b4cebbb1c58, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

add-branding 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 26d 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.

.agents/skills/add-branding/SKILL.md · 127 lines

How it starts

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

Before starting: git fetch origin && gh pr list --state open && git log origin/main --oneline -3 — if another agent has an open PR touching the same files you need, wait for it to merge, then branch from fresh origin/main.

Help the user customize the Mozaiks app shell using declarative config.

Key Files

Read these first:

app/app.json — App identity, auth, admin emails
app/config/shell.json — Shell chrome config
app/config/ai.json — Startup mode, workflow entry point
app/brand/theme_config.json — Theme tokens

For assets:

app/brand/assets/ — Logos, icons
app/brand/fonts/ — Custom fonts

Questions to Ask

Changing visuals, shell behavior, or both?
Should app open on chat, a page, or adapter route?
Should chat start in ask mode or workflow mode?
Changing logos, icons, or fonts?
Any auth changes?

What Each File Controls

File	Controls
`app/app.json`	App name, auth requirement, admin emails, startup landing spot
`app/brand/theme_config.json`	Colors, fonts, spacing, dark/light mode, shell chrome
`app/config/shell.json`	Compact shell shortcuts, navigation policy, chrome mode policy, plus header/footer/profile/notification/mobile overrides
`app/config/ai.json`	Entry workflow, startup mode

Rules

Do NOT invent files like brand.json, ui.json, or auth.json — these don't exist
Prefer declarative config changes over React code changes
Keep workflow startup settings in ai.json
Shell branding (logos, fonts, login theme) belongs in app/brand/
app/app.json is for app identity and startup intent — not colors or shell chrome
Prefer app/config/shell.json -> shortcuts for common shell items so the file stays small.
Prefer route-level ui/pages/*.yaml -> navigation for page-owned navigation entries; use app/config/shell.json -> navigation.policy for app-wide placement rules.
Prefer route-level ui/pages/*.yaml -> shell_mode for per-route header/footer/bottom-bar behavior; use app/config/shell.json -> chrome only for app-wide mode defaults.
Use explicit header, profile, notifications, footer, or mobile objects only when labels, icons, roles, or paths need custom overrides.
Common shortcut ids include home, apps, workspace, wallet, create, profile, messages, notifications, settings, admin, support, signout, signin, legal, terms, cookies, and privacy. Use dashboard only when the app declares a page or route with id dashboard.

Read the full file on GitHub · 127 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.

26d ago Changed 3b4cebbb1c58
2mo ago First seen · 127 lines · 31 tokens per session scan A 0579b796da8d

Subscribe to this mod's changes

add-branding is a skill published in the GitHub repository BlocUnited-LLC/mozaiks (24 stars, last pushed yesterday), licensed MIT. It adds 31 tokens to every session and 1,174 once invoked, about $0.0001 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.

Design and UX Frontend LLM agent-framework agentic-ai ai ai-agents genai

add-branding next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
add-brandingBlocUnited-LLC/mozaiks	Skill	24	yesterday	MIT	A	31	Claude Code
building-pydantic-ai-agentspydantic/pydantic-ai	Skill	21k	yesterday	MIT	A	92	Claude Code, Codex
pydantic-ai-harnesspydantic/pydantic-ai	Skill	21k	yesterday	MIT	A	197	Claude Code, Codex
migrating-langchain-to-pydantic-aipydantic/pydantic-ai	Skill	21k	yesterday	MIT	A	100	Codex
migrating-vercel-ai-sdk-and-eve-to-pydantic-aipydantic/pydantic-ai	Skill	21k	yesterday	MIT	A	107	Codex
migrating-claude-agent-sdk-to-pydantic-aipydantic/pydantic-ai	Skill	21k	yesterday	MIT	A	90	Codex
migrating-mastra-to-pydantic-aipydantic/pydantic-ai	Skill	21k	yesterday	MIT	A	73	Codex

mozaiks: Skill for Claude Code