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.
curl -O https://raw.githubusercontent.com/BlocUnited-LLC/mozaiks/main/.agents/skills/add-branding/SKILL.mdgit clone --depth 1 https://github.com/BlocUnited-LLC/mozaiksWrote 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/blocunited-llc/mozaiks/add-branding)<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.
<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>- 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.00031 | $0.01173 |
| Opus 5 | $0.00015 | $0.00587 |
| Sonnet 5 | $0.00006 | $0.00235 |
| Haiku 4.5 | $0.00003 | $0.00117 |
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 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 — 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 or branch off it instead of main.
Help the user customize the Mozaiks app shell using declarative config.
Key Files
Read these first:
app/app.json— App identity, auth, admin emailsapp/config/shell.json— Shell chrome configapp/config/ai.json— Startup mode, workflow entry pointapp/brand/theme_config.json— Theme tokens
For assets:
app/brand/assets/— Logos, iconsapp/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
askmode orworkflowmode? - 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, orauth.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.jsonis for app identity and startup intent — not colors or shell chrome- Prefer
app/config/shell.json -> shortcutsfor common shell items so the file stays small. - Prefer route-level
ui/pages/*.yaml -> navigationfor page-owned navigation entries; useapp/config/shell.json -> navigation.policyfor app-wide placement rules. - Prefer route-level
ui/pages/*.yaml -> shell_modefor per-route header/footer/bottom-bar behavior; useapp/config/shell.json -> chromeonly for app-wide mode defaults. - Use explicit
header,profile,notifications,footer, ormobileobjects 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, andprivacy. Usedashboardonly when the app declares a page or route with iddashboard.
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 · 127 lines · 31 tokens per session scan A 0579b796da8d
add-branding is a skill published in the GitHub repository BlocUnited-LLC/mozaiks (25 stars, last pushed today), licensed MIT. It adds 31 tokens to every session and 1,173 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
web-design
Penguin visual language for generated web pages and app UIs — GitHub-style simplicity with a single blue accent, light and pure-black dark themes, design tokens, component and chat-interface recipes, plus an opt-in warm paper editorial theme.
ui-craft
Design, build, redesign, or modify browser-visible web interfaces with product-quality composition, visual systems, interaction states, responsive behavior, accessibility, and browser visual QA. Use for HTML, CSS, JavaScript, React, Vue, or Svelte pages and components, landing pages, dashboards, admin tools, settings…
accessibility-a11y
Semantic HTML, keyboard navigation, focus states, ARIA labels, skip links, and WCAG contrast requirements. Use when ensuring accessibility compliance, implementing keyboard navigation, or adding screen reader support.
tailwind-shadcn
Tailwind CSS utility patterns with shadcn/ui component usage, theming via CSS variables, and responsive design. Use when styling components, installing shadcn components, implementing dark mode, or creating consistent design systems.
anti-slop-frontend
A mechanical, countable anti-slop checklist for AI-generated frontend. Catches the specific signatures an undirected model defaults to: AI-purple glows, Inter-everywhere, em-dashes, div-based fake screenshots, eyebrow-on-every-section, beige+brass "premium" palettes, generic Jane Doe / Acme data. Advisory layer that…
frontend-mockup-loop
Plan, build, and iterate UX-friendly frontend mockups via a ground→contract→mockup→test→fix→learn loop, acting as an expert UX designer who grounds every decision in externally documented public design rules (Nielsen heuristics, Laws of UX, WCAG, GOV.UK/USWDS/Material). Uses the bundled servemockup, scoremockup, and…