gsp-brand-brief

gsp-brand-brief is a skill for Claude Code from jubscodes/get-shit-pretty. It costs 0 tokens per session (2,393 once invoked), scanned A, original, MIT.

A guided starting point for defining a new brand: who it serves, why it exists, and how it should feel.

In plain words
What is it for?
Use it to create the initial brand brief, configuration, project state, and roadmap before researching the market or designing the identity.
Why use it?
It turns vague brand ideas into a written brief and project structure that later branding steps can use.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter. Also seen: mentions CLAUDE.md; names the AskUserQuestion tool.

Good fit Use it to create the initial brand brief, configuration, project state, and roadmap before researching the market or designing the identity.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jubscodes/get-shit-pretty/gsp-brand-brief
Install

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.

Any agent
npx skills add jubscodes/get-shit-pretty --skill gsp-brand-brief
Clone the repo
git clone --depth 1 https://github.com/jubscodes/get-shit-pretty

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.

agentmods badge for gsp-brand-brief

README.md
[![agentmods](https://agentmods.dev/badge/skills/jubscodes/get-shit-pretty/gsp-brand-brief/github.svg)](https://agentmods.dev/skills/jubscodes/get-shit-pretty/gsp-brand-brief)
Your own site
<a href="https://agentmods.dev/skills/jubscodes/get-shit-pretty/gsp-brand-brief"><img src="https://agentmods.dev/badge/skills/jubscodes/get-shit-pretty/gsp-brand-brief/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.

agentmods 80×15 button for gsp-brand-brief

Your own site · 80×15
<a href="https://agentmods.dev/skills/jubscodes/get-shit-pretty/gsp-brand-brief"><img src="https://agentmods.dev/badge/skills/jubscodes/get-shit-pretty/gsp-brand-brief.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,393 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.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.02393
Opus 5 $0.00000 $0.01196
Sonnet 5 $0.00000 $0.00479
Haiku 4.5 $0.00000 $0.00239

Measured 11d ago against content hash 9f3926064d25, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

gsp-brand-brief 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.

gsp/skills/gsp-brand-brief/SKILL.md · 175 lines

How it starts

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

Works two ways:

  1. Routed/gsp-start detects "new brand" intent and invokes this skill
  2. Direct — user runs /gsp-brand-brief directly

This skill handles new brands only. For existing brands (evolve mode), /gsp-start routes to /gsp-brand-audit directly.

Input: Brand name (from args or asked) Output: .design/branding/{name}/ with BRIEF.md, STATE.md, config.json, ROADMAP.md Next: /gsp-brand-research

<questioning_principles> One decision per question. Every question must be its own AskUserQuestion call. Ask one thing, wait for the answer, use it to inform the next question.

Never re-ask what the user already answered. If you need to validate, confirm: "I see X from earlier — still accurate?"

Inference over interrogation. Don't ask what you can infer. "Fintech for Gen Z" → mobile-first, modern, trustworthy. State inferences, let them correct.

Concrete options over open-ended. "More like Stripe's clean approach or Duolingo's playful style?" beats "What style do you want?" Use AskUserQuestion with 2-3 options when the option space is known.

Adapt and skip. If an early answer reveals enough, skip later questions. Follow up on surprises before moving on. The sequence is a guide, not a script.

Know when you have enough. A brand brief is complete when you can answer:

  • Who is this for and what do they need?
  • What does the brand feel like?
  • What are the hard constraints? </questioning_principles>

Check if a brand name was passed via invocation args. If not, ask:

  1. Ask for brand name (kebab-case, e.g., "acme-corp") — AskUserQuestion

Validate: lowercase alphanumeric + hyphens only. Check .design/branding/{name}/ doesn't already exist. If it does, use AskUserQuestion: Overwrite / Pick a different name.

Accept an optional e2e flag from the invoking skill. Default to false.

Create directory structure:

mkdir -p .design/branding/{name}/{discover,strategy,identity,patterns}

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

  1. 11d ago First seen · 175 lines · 0 tokens per session scan A 9f3926064d25

Subscribe to this mod's changes

gsp-brand-brief is a skill published in the GitHub repository jubscodes/get-shit-pretty (54 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,393 tokens. 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.

Related

Other skills, from other repositories

opencli-usage

Use at the start of any OpenCLI session — this is the top-level map of what opencli can do, how to discover adapters, what flags and output formats are universal, and which specialized skill to load next. Point here when an agent asks "what can opencli do?" or "how do I find the right command?".

jackwener/OpenCLI · 74 tokens

opencli-sitemap-author

Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.

jackwener/OpenCLI · 67 tokens

opencli-browser-sitemap

Use when driving a website with opencli browser and sitemap context is available, requested, or needed to avoid blind navigation. Guides agents to consume site sitemap files lazily, choose adapter/browser fallback paths, resume from state signatures, and mark stale sitemap entries without trusting them over live…

jackwener/OpenCLI · 64 tokens

antv-x6-editor

A skill for creating and troubleshooting interactive diagrams with AntV X6, a JavaScript engine for editors made of connected nodes and lines. It supports diagram types such as flowcharts, dependency graphs, entity-relationship diagrams, and organization charts.

antvis/chart-visualization-skills · 253 tokens

gpt-vis

A chart-generation tool that recommends visual formats for data and produces either chart settings or runnable code. It uses GPT-Vis, a library for rendering data visualisations.

antvis/chart-visualization-skills · 63 tokens

infographic-creator

Create beautiful infographics based on given text content. Use when users request to create infographics.

antvis/chart-visualization-skills · 24 tokens