brand-brief

brand-brief is a skill for Claude Code from Mora-AI-Content-Studio/mora-claude-plugin. It costs 71 tokens per session (709 once invoked), scanned A, original, MIT.

A factual summary of a Mora AI business, including what it sells, who it serves, how it sounds, and its current catalogue. Mora AI is the connected service that stores these brand details.

In plain words
What is it for?
Preparing a brand handoff, investor or sales pitch, advertising copy, or other work done outside Mora AI.
Why use it?
It gives designers, writers, or pitch teams reliable brand information instead of relying on memory or invented details.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the mora plugin — 6 skills, 1 MCP server shipped together

Good fit Preparing a brand handoff, investor or sales pitch, advertising copy, or other work done outside Mora AI.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mora-ai-content-studio/mora-claude-plugin/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 Mora-AI-Content-Studio/mora-claude-plugin --skill brand-brief
Clone the repo
git clone --depth 1 https://github.com/Mora-AI-Content-Studio/mora-claude-plugin

Made for: Claude Code.

Or install mora, the plugin that ships this one along with the rest of its 6 skills, 1 MCP server.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/mora-ai-content-studio/mora-claude-plugin/brand-brief/github.svg)](https://agentmods.dev/skills/mora-ai-content-studio/mora-claude-plugin/brand-brief)
Your own site
<a href="https://agentmods.dev/skills/mora-ai-content-studio/mora-claude-plugin/brand-brief"><img src="https://agentmods.dev/badge/skills/mora-ai-content-studio/mora-claude-plugin/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 brand-brief

Your own site · 80×15
<a href="https://agentmods.dev/skills/mora-ai-content-studio/mora-claude-plugin/brand-brief"><img src="https://agentmods.dev/badge/skills/mora-ai-content-studio/mora-claude-plugin/brand-brief.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 71 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 709 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.00071 $0.00709
Opus 5 $0.00036 $0.00354
Sonnet 5 $0.00014 $0.00142
Haiku 4.5 $0.00007 $0.00071

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

Security

Grade A, and why

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 10d 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.

skills/brand-brief/SKILL.md · 51 lines

How it starts

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

Brand Brief

Produce a portable, factual summary of a user's real business — pulled from their own Mora account, not written from a guess — for use in work that happens outside Mora entirely. The brief itself is the deliverable here, not a step toward writing new social content.

When to use this

Trigger when the user wants their brand facts summarized or handed off for use elsewhere: briefing a designer or freelancer, prepping a pitch or investor update, writing ad copy on a platform Mora doesn't touch, or any variant of "what does my brand actually sell / sound like." This is distinct from the content-performance-audit skill (which is about what has performed) and from ordinary content drafting inside Mora (which should call get_brand_profile itself as a grounding step, not go through this skill).

Procedure

  1. Call get_brand_profile — business name, what it sells, who it sells to, and its voice.
  2. Call list_products (no search filter, default limit) to pull the current catalogue.
  3. Assemble a single brief with these sections, using only what the tools returned:
    • Business — name, one-line description of what it sells, from get_brand_profile.
    • Audience — who it sells to, verbatim from what the tool returned, not elaborated.
    • Voice — the brand voice as described, quoted or closely paraphrased, not reinvented.
    • Catalogue — a compact list of products from list_products: title, price (min_price), and a short line from description if present. If the user asked about a specific product or category, call list_products again with a search substring instead of filtering a full list by eye.
  4. Keep the brief tight and copy-pasteable — this is meant to be dropped into an email, a doc, or a prompt for other work, not read as a report. Do not pad it with commentary or marketing language of your own; the value is that every fact in it is real.

Honest emptiness

If get_brand_profile returns thin or missing fields, say plainly which facts are not on record in Mora — do not invent a name, description, audience, or voice to fill a gap. A missing brand profile means brand setup hasn't been completed in Mora, not that the business has no identity; say that directly and suggest completing it in Mora rather than guessing on the user's behalf.

Read the full file on GitHub · 51 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. 10d ago First seen · 51 lines · 71 tokens per session scan A f3bb123f0549

Subscribe to this mod's changes

brand-brief is a skill published in the GitHub repository Mora-AI-Content-Studio/mora-claude-plugin (0 stars, last pushed 20d ago), licensed MIT. It adds 71 tokens to every session and 709 once invoked, about $0.0004 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-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens