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 Davidhevesi/marketing-skills-repo --skill brand-voicegit clone --depth 1 https://github.com/Davidhevesi/marketing-skills-repoWrote 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/davidhevesi/marketing-skills-repo/brand-voice)<a href="https://agentmods.dev/skills/davidhevesi/marketing-skills-repo/brand-voice"><img src="https://agentmods.dev/badge/skills/davidhevesi/marketing-skills-repo/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/davidhevesi/marketing-skills-repo/brand-voice"><img src="https://agentmods.dev/badge/skills/davidhevesi/marketing-skills-repo/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.00038 | $0.04024 |
| Opus 5 | $0.00019 | $0.02012 |
| Sonnet 5 | $0.00008 | $0.00805 |
| Haiku 4.5 | $0.00004 | $0.00402 |
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 12d 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 — 447 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brand Voice
You help users define, document, and consistently apply their brand voice across every piece of content and communication. Brand voice is how a business sounds — its personality expressed through words. This skill captures that voice in concrete, usable terms so that every output (copy, emails, social posts, proposals, content) sounds unmistakably like the same brand.
The output is a Brand Voice Guide stored as a knowledge file in the user's Claude Project. Every other content and copy skill references it.
Why This Matters
Most businesses have a voice — they just haven't written it down. The result: every piece of content sounds slightly different depending on who wrote it, what mood they were in, or what template they found online. The brand sounds like a committee instead of a person.
This skill fixes that. A documented brand voice means:
- Every output sounds consistent whether you wrote it at 8am or 11pm
- You spend less time editing copy that "doesn't sound right"
- Claude can match your voice without trial-and-error on every task
- When you bring in help (contractors, VAs, tools), they have a reference
Before You Start
Check for Business Context
Look for a Business Context document in the project knowledge files.
If it exists: Read it first. The Brand Voice section (Section 8) already has a starting point — tone spectrums, personality adjectives, communication style, inspiration, and writing rules. Use that as the foundation and go deeper. Don't re-ask what's already answered.
If it doesn't exist: Say — "Before we build your brand voice guide, it helps to have your business context set up. That captures who you are, who you serve, and what you stand for — all of which shape how you should sound. Want to do that first, or should we build the voice guide independently?"
If they want to proceed independently, gather the basics: what the business does, who it serves, what it stands for. You need enough context to make voice decisions meaningful.
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.
- 12d ago First seen · 447 lines · 38 tokens per session scan A 96a63c3765da
brand-voice is a skill published in the GitHub repository Davidhevesi/marketing-skills-repo (5 stars, last pushed 5mo ago), licensed MIT. It adds 38 tokens to every session and 4,024 once invoked, about $0.0002 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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…