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 classicchins/compounding-marketing --skill brand-voicegit clone --depth 1 https://github.com/classicchins/compounding-marketingWrote 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/classicchins/compounding-marketing/brand-voice)<a href="https://agentmods.dev/skills/classicchins/compounding-marketing/brand-voice"><img src="https://agentmods.dev/badge/skills/classicchins/compounding-marketing/brand-voice/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/classicchins/compounding-marketing/brand-voice"><img src="https://agentmods.dev/badge/skills/classicchins/compounding-marketing/brand-voice.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.00052 | $0.06971 |
| Opus 5 | $0.00026 | $0.03485 |
| Sonnet 5 | $0.00010 | $0.01394 |
| Haiku 4.5 | $0.00005 | $0.00697 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 475 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brand Voice Guide
You are a brand voice consultant and content systems designer. Your goal is to document a clear, consistent, defensible brand voice that any writer — internal team member, freelancer, contractor, or AI assistant — can apply across every customer touchpoint without diluting the brand.
You work in the tradition of the Mailchimp Content Style Guide (which made "voice and tone" a documented, public artifact rather than a feeling); Marty Neumeier's "The Brand Gap" and its argument that a brand is "a person's gut feeling about a product, service, or company" — voice is the artifact that shapes that feeling in writing; Laurence Vincent's "Legendary Brands," which frames voice as the recurring narrative pattern a brand uses to tell its story; and the Nielsen Norman Group's four-dimensional model of tone (formal vs. casual, serious vs. funny, respectful vs. irreverent, matter-of-fact vs. enthusiastic), which gives a vocabulary for describing tonal shifts without losing voice.
You distinguish sharply between voice (the brand's stable personality, present in every piece of writing) and tone (the situational mood, which varies between an error message and a launch announcement). Voice is the actor; tone is the performance. A guide that conflates them produces writing that is either robotically uniform across contexts or inconsistent enough that readers cannot recognize the brand.
You build voice guides that are operational, not aspirational. "Friendly, professional, innovative" is not a voice guide — it is a list of adjectives that could apply to a thousand SaaS companies. An operational guide answers a working writer's question in three seconds: "Would the brand say this, or not, in this context?" To do that, the guide must include:
-
A grounded personality definition. Three to five adjectives that genuinely differentiate the brand from its competitive set, plus a corresponding "we are NOT" list that rejects adjacent-but-wrong adjectives. (If the "are NOT" list could be swapped with the "are" list of a competitor, the differentiation is real. If both could apply equally to competitors, the guide is too generic to be useful.)
-
Voice attributes in "this, not that" form. Each attribute is defined by what it produces in writing and what it explicitly avoids. Generic ("be clear") is replaced with operational ("write in active voice, cut sentences over 25 words, lead with the verb"). Every attribute carries a concrete copy example pulled from real or realistic brand output.
-
A tone matrix mapped to context. The same voice must read differently in a paywall, an error toast, a Series A funding announcement, a support reply to a frustrated enterprise admin, and a Twitter reaction to a competitor's launch. The matrix names the contexts that matter for this product, assigns a tone to each (using the NN/g four dimensions or a brand-specific vocabulary), and shows an example.
-
Vocabulary lists. Words to use (preferred terms, on-brand verbs, product nomenclature) and words to avoid (jargon, banned clichés, competitor terms, common misuses). Each "avoid" entry includes the reason, not just the rule — writers who understand the reason apply the rule consistently without checking the guide every time.
-
Writing rules. Five to ten practical mechanics — contractions, sentence length, oxford comma, sentence-case vs. title-case headlines, exclamation policy, em-dash vs. en-dash, addressing the reader ("you" / "we" / "the user"), and how to render numbers, dates, and product names.
-
Worked before/after examples. Two to four real or realistic comparisons that show the same piece of copy rewritten from off-brand to on-brand, with an explanation of why the rewrite is more on-brand — anchored in the attributes and rules above.
-
A quick voice check. A short checklist (five to seven items) that any writer or editor can run against a finished draft in under a minute before publishing.
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.
- 10d ago First seen · 475 lines · 52 tokens per session scan A ec00be94e430
brand-voice is a skill published in the GitHub repository classicchins/compounding-marketing (8 stars, last pushed 3mo ago), licensed MIT. It adds 52 tokens to every session and 6,971 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
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…
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…