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 agentmods add skills/mountainunicorn/add/brand-updatenpx skills add MountainUnicorn/add --skill brand-updategit clone --depth 1 https://github.com/MountainUnicorn/addWrote 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/mountainunicorn/add/brand-update)<a href="https://agentmods.dev/skills/mountainunicorn/add/brand-update"><img src="https://agentmods.dev/badge/skills/mountainunicorn/add/brand-update.svg" alt="Measured on agentmods" 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.00020 | $0.01700 |
| Opus 5 | $0.00010 | $0.00850 |
| Sonnet 5 | $0.00004 | $0.00340 |
| Haiku 4.5 | $0.00002 | $0.00170 |
Grade A, and why
brand-update 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 5d 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 — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ADD Brand Update Command v{{VERSION}}
Update the project's branding configuration with new materials and audit existing generated artifacts for brand consistency. Optionally apply fixes to bring artifacts in line with the new brand.
Pre-Flight
- Check if
.add/config.jsonexists. If not, tell the user to run/add:initfirst. - Read
.add/config.jsonand extract the currentbrandingsection. - Read
${CLAUDE_PLUGIN_ROOT}/templates/presets.jsonfor available presets and palette generation algorithm.
Arguments
The user provided: $ARGUMENTS
If arguments contain specific values (hex color, preset name, etc.), use them directly instead of asking.
Phase 1: Collect New Branding
Step 1.1: Determine Update Scope
Use AskUserQuestion:
Question: "What would you like to update?"
Options:
- "Accent color only"
- "Full brand refresh (color, fonts, tone, logo)"
- "Apply a color preset"
Step 1.2a: Accent Color Only
Use AskUserQuestion:
Question: "Choose a new accent color:"
Options:
- "Raspberry (#b00149) — bold and warm"
- "AI Purple (#6366f1) — classic tech"
- "Ocean (#0891b2) — professional and calm"
- "Custom hex color"
If "Custom hex color": Ask for the hex value. Validate it's a valid 3 or 6 character hex color (with or without #).
Generate the full palette from the selected color using the algorithm in ${CLAUDE_PLUGIN_ROOT}/templates/presets.json:
- Parse hex to RGB, convert to HSL
- Generate all palette values (accentLight, accentDark, accentMuted, accentGlow, gradientStart, gradientMid, gradientEnd)
- Keep fixed colors (success: #22c55e, warning: #eab308, info: #0ea5e9)
Step 1.2b: Full Brand Refresh
Ask each in sequence:
Color: Same as Step 1.2a above.
Fonts: "Do you have font preferences?" Use AskUserQuestion:
- "Use system defaults (Recommended)"
- "Let me specify fonts"
If specifying: Ask for heading font, body font, code font. Store in branding.fonts.
Tone: "Describe your brand's tone/voice in a few words (e.g., 'professional but approachable', 'bold and confident', 'technical and precise')." (Default: null — no tone constraint)
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.
- 5d ago First seen · 225 lines · 20 tokens per session scan A c68d2e119c2c
brand-update is a skill published in the GitHub repository MountainUnicorn/add (11 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 1,700 once invoked, about $0.0001 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
swarm
Launching multi-agent parallel work with the Agentic SDLC. Use when a task benefits from decomposition into parallel subtasks.
finish
Completing a development branch for merge readiness. Use when implementation and tests pass and the branch needs formal preparation for review and merge.
grill
Interrogating requirements to validate before building. Use before swarm decomposition, design decisions on ambiguous features, or when scope creep risk is high.
team
Referencing the agent roster, roles, coordination model, and dispatch modes. Use when spawning agents or checking permissions.
triage
Triage insights into actionable GitHub issues across repos. Use after running /insights to convert analysis into tracked work.
ticket
Associate every PDS task with a GitHub issue. Orchestrator finds or creates the ticket, posts plan and acceptance criteria as a checkbox list, updates it as work progresses. Use at Phase 1 of every swarm.