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 sanky369/vibe-building-skills --skill brand-voicegit clone --depth 1 https://github.com/sanky369/vibe-building-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/sanky369/vibe-building-skills/brand-voice)<a href="https://agentmods.dev/skills/sanky369/vibe-building-skills/brand-voice"><img src="https://agentmods.dev/badge/skills/sanky369/vibe-building-skills/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/sanky369/vibe-building-skills/brand-voice"><img src="https://agentmods.dev/badge/skills/sanky369/vibe-building-skills/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.00137 | $0.01868 |
| Opus 5 | $0.00068 | $0.00934 |
| Sonnet 5 | $0.00027 | $0.00374 |
| Haiku 4.5 | $0.00014 | $0.00187 |
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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brand Voice
Produce a voice guide: a compact, enforceable document that makes every future piece of copy sound like the same brand, whoever (or whatever) writes it. Voice is how the brand sounds; positioning is what it claims — keep them separate. The governing principle: a voice guide is only real if it changes sentences. Every rule in it must be concrete enough that you can point at a line of copy and say pass or fail.
When to use / when not to
- Use before writing copy at scale, when content across channels sounds inconsistent, or when the user asks for tone/voice/brand guidelines.
- If the user's actual problem is what to say — differentiation, the core claim — use
skills/marketing/positioning-anglesfirst; voice without positioning is a costume on an empty claim. - If the user wants one specific page written, use
skills/marketing/direct-response-copy(it consumes the voice guide; a lightweight voice sketch from its own intake is acceptable if no guide exists). - Audit mode: if a voice guide already exists and the user says "our content drifted", skip to Step 6 and score existing content against the guide.
Intake
Ask in one batch, only for what's missing from context:
- What do you sell and to whom? (If a positioning statement exists from
skills/marketing/positioning-angles, use it — don't re-ask.) - Paste 2–3 samples of your current writing (site copy, emails, posts) — or share a URL.
- Name 2–3 brands or writers whose voice you admire, and one you never want to sound like.
- Any words your brand insists on or bans?
Don't stall: if samples or a site exist, infer answers 3–4 from them, state your inferences as assumptions, and proceed.
Workflow
1. Extract the current voice (if any content exists)
Before prescribing, describe. Read the samples and write a 3-line diagnosis: what the voice currently is, where it's inconsistent, what's distinctive worth keeping. Skip only for pre-launch brands with no content.
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 · 132 lines · 137 tokens per session scan A ee7809c28ffc
brand-voice is a skill published in the GitHub repository sanky369/vibe-building-skills (30 stars, last pushed 2mo ago), licensed MIT. It adds 137 tokens to every session and 1,868 once invoked, about $0.0007 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-30.
Other skills, from other repositories
api-tester
A tool for creating and checking API tests from the real API contract and implementation. An API is the agreed way that software sends requests and receives responses.
dep-auditor
A read-only audit of a project’s third-party packages for known security issues, version health, and license facts. It uses the versions actually selected by lockfiles, which record the exact packages installed, rather than relying only on version ranges.
skill-curator
A Chinese-language evaluator for deciding whether developer tools and agent resources are suitable for a curated collection. It checks real repositories, installation paths, activity, duplicates, and security boundaries using evidence.
git-workflow
A guide for handling Git repository work safely, including status checks, branches, commits, pushes, pull requests, and rebasing. Git is a version-control system that records code changes and coordinates work between developers.
zh-readme
A tool for writing README files in Chinese after first examining a software project. A README is the main guide visitors see when they open a code repository.
env-manager
An environment-variable manager for project settings stored outside the code, often in .env files. It checks variable definitions and usage while keeping secret values out of reports and terminal output.