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 skills add w95/awesome-claude-corporate-skills --skill brand-voice-enforcementgit clone --depth 1 https://github.com/w95/awesome-claude-corporate-skillsWrote 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/w95/awesome-claude-corporate-skills/brand-voice-enforcement)<a href="https://agentmods.dev/skills/w95/awesome-claude-corporate-skills/brand-voice-enforcement"><img src="https://agentmods.dev/badge/skills/w95/awesome-claude-corporate-skills/brand-voice-enforcement/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/w95/awesome-claude-corporate-skills/brand-voice-enforcement"><img src="https://agentmods.dev/badge/skills/w95/awesome-claude-corporate-skills/brand-voice-enforcement.svg" alt="Reviewed on agentmods" width="80" 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.00156 | $0.01133 |
| Opus 5 | $0.00078 | $0.00566 |
| Sonnet 5 | $0.00031 | $0.00227 |
| Haiku 4.5 | $0.00016 | $0.00113 |
Grade A, and why
brand-voice-enforcement 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 9d 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.
This is a copy
100% identical to brand-voice-enforcement — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brand Voice Enforcement
Apply existing brand guidelines to all sales and marketing content generation. Load the user's brand guidelines, apply voice constants and tone flexes to the content request, validate output, and explain brand choices.
Loading Brand Guidelines
Find the user's brand guidelines using this sequence. Stop as soon as you find them:
-
Session context — Check if brand guidelines were generated earlier in this session (via
/brand-voice:generate-guidelines). If so, they are already in the conversation. Use them directly. Session-generated guidelines are the freshest and reflect the user's most recent intent. -
Local guidelines file — Check for
.claude/brand-voice-guidelines.mdinside the user's working folder. Do NOT use a relative path from the agent's current working directory — in Cowork, the agent runs from a plugin cache directory, not the user's project. Resolve the path relative to the user's working folder. If no working folder is set, skip this step. -
Ask the user — If none of the above found guidelines, tell the user: "I couldn't find your brand guidelines. You can:
- Run
/brand-voice:discover-brandto find brand materials across your platforms - Run
/brand-voice:generate-guidelinesto create guidelines from documents or transcripts - Paste guidelines directly into this chat or point me to a file"
Wait for the user to provide guidelines before proceeding.
- Run
Also read .claude/brand-voice.local.md for enforcement settings (even if guidelines came from another source):
strictness: strict | balanced | flexiblealways-explain: whether to always explain brand choices
Enforcement Workflow
1. Analyze the Content Request
Before writing, identify:
- Content type: email, presentation, proposal, social post, message, etc.
- Target audience: role, seniority, industry, company stage
- Key messages needed: which message pillars apply
- Specific requirements: length, format, tone overrides
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.
- 9d ago First seen · 108 lines · 156 tokens per session scan A 3da527576a05
brand-voice-enforcement is a skill published in the GitHub repository w95/awesome-claude-corporate-skills (198 stars, last pushed 6mo ago), licensed MIT. It adds 156 tokens to every session and 1,133 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to brand-voice-enforcement, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
design-por-referencia
Use when a landing page, marketing site, or hero section looks generic/AI-made ("cara de vibe coding") and needs a $10k-agency-level redesign, or when building a new landing from scratch. Triggers - "o site ficou com cara de IA", "quero uma landing premium", "redesenha a landing", "faz o site baseado em [site de…
lighthouse-95
Use when a website must score 95+ in every Lighthouse category (Performance, Accessibility, Best Practices, SEO), when scores are stuck below target, or when diagnosing poor FCP, LCP, TBT, or CLS on a deployed site.
seo-validate
SEO validator: meta/OG, Schema.org, hreflang, Core Web Vitals, crawlability. Triggers: SEO, meta tags, Schema.org, hreflang, LCP, INP, CLS, Core Web Vitals, sitemap, crawlability.
debug
Systematic debugging via logs, health checks, hypothesis-driven investigation. Triggers: debug, error, trace root cause, fix bug, reproduce symptom, investigation.
pr
Creates GitHub PR after pre-flight checks (lint/typecheck/tests), structured summary from commits. Triggers: pr, pull request, create PR, ready to merge.
research-mastery
Hierarchical retrieval: KB → MCP/Context7 → web. Triggers: research, fact-check, verify, synthesize, cross-reference, multi-source, cite sources.