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/localplugins/plugins/brand-voicenpx skills add localplugins/plugins --skill brand-voicegit clone --depth 1 https://github.com/localplugins/pluginsWhat 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 | $0.00076 | $0.01197 |
| Opus 5 | $0.00038 | $0.00598 |
| Sonnet 5 | $0.00015 | $0.00239 |
| Haiku 4.5 | $0.00008 | $0.00120 |
Grade A, and why
brand-voice 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 yesterday.
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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brand Voice
Overview
Brand Voice loads the team's saved brand profile and applies it so every asset sounds like the team, not like generic AI. It governs voice, messaging, style, and compliance for all content the plugin produces.
The profile is a set of Markdown files the team owns in its own repository.
Four files define the brand: brand-voice.md (personality, tone, signature phrases, words to avoid),
messaging.md (positioning, value props, personas, boilerplate),
style-guide.md (formatting, glossary, product and trademark casing, banned words, inclusive language),
and compliance.md (approved claims, prohibited terms, required disclaimers).
This skill is instruction-driven: it reads those files and writes on-brand copy, with no accounts, keys, or network access.
Prerequisites
- A brand profile in
content/brand/(default) orcontent/brands/<name>/when a brand is named, optionally withcontent/brand/locales/<xx-XX>/overrides. Create one with/brand-setup. - Read access to the profile files. The skill uses Glob to locate them, Read to load them, and Write to save finished copy.
- No external services. All judgment comes from the profile files, never general opinion.
Instructions
- Check for an active brand profile: Glob
content/brand/, orcontent/brands/<name>/when a brand is named, plus any matchinglocales/<xx-XX>/directory. - Read all four profile files. Locale files override the base file of the same name field-by-field.
- Set the working voice from
brand-voice.md: personality adjectives, tone, do and don't rules, signature phrases, and the words-to-avoid list. - Apply messaging from
messaging.md: pick the persona and the key message the asset reinforces, and reuse approved value props and boilerplate. - Configure the style layer while drafting: formatting rules, glossary terms, exact product and trademark casing, banned words, and inclusive-language rules.
- Verify compliance against
compliance.md: use only approved claims, include every required disclaimer, and remove any prohibited term. - Run the self-check before returning: confirm no word-to-avoid, no banned word, correct casing, and required disclaimers present. Revise until clean.
- When no profile is found, tell the user to run
/brand-setupand offer to proceed with sensible defaults for this run only.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 92 lines · 76 tokens per session scan A a74fda1dedf5
brand-voice is a skill published in the GitHub repository localplugins/plugins (5 stars, last pushed 1mo ago), licensed MIT. It adds 76 tokens to every session and 1,197 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.
Other skills, from other repositories
code-to-content
Use when transforming a codebase into developer content. Activates for: Blog posts, tutorials, or technical documentation about code README, changelog, release notes, or API docs generation Twitter/X threads, LinkedIn posts about technical work Conference talk proposals (CFP) or newsletter content Build-in-public…
brainstorm-okrs
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.
pre-mortem
Run a pre-mortem risk analysis on a PRD or launch plan. Categorizes risks as Tigers (real problems), Paper Tigers (overblown concerns), and Elephants (unspoken worries), then classifies as launch-blocking, fast-follow, or track. Use when preparing for launch, stress-testing a product plan, or identifying what could go…
ab-test-analysis
Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
retro
Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.