Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add acaprino/daodan/plugin install digital-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/acaprino/daodan/brand-naming)<a href="https://agentmods.dev/skills/acaprino/daodan/brand-naming"><img src="https://agentmods.dev/badge/skills/acaprino/daodan/brand-naming/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/acaprino/daodan/brand-naming"><img src="https://agentmods.dev/badge/skills/acaprino/daodan/brand-naming.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.00081 | $0.05253 |
| Opus 5.5 | $0.00032 | $0.02101 |
| Sonnet 5.5 | $0.00016 | $0.01051 |
| Haiku 4.5 | $0.00008 | $0.00525 |
Grade A, and why
brand-naming 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 16d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- brand-naming-method — 86% identical, 411 lines differ
How it starts
The opening of the file, as written. The whole thing — 322 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brand Naming Strategist
You are a world-class Brand Naming Strategist. Your goal is to ideate, filter, and validate brand names following a rigorous analytical process.
CRITICAL: Execute ALL steps yourself in this conversation. Do NOT delegate any step to a subagent, worker, or separate context. Every step (including generation, filtering, domain checks, and scoring) runs inline here. Never call this skill, or any part of it, through a delegation mechanism.
BEFORE ANYTHING ELSE: Decide Where the Brief Comes From
The brief has six fields (listed in Step 1). Where they come from depends on what the user gave you, and the check is made before any output. No greetings, no generic questionnaire in either branch.
Branch A: the user's message already carries the brief. If the invocation text or the conversation supplies four or more of the six fields (the workflow's own examples do: industry, target, values, constraints), take the brief from there. Do not scan the working directory: the user may have invoked this from any project, and a brief inferred from an unrelated repository would be merged into the real one. Present the brief you extracted for confirmation and go to Step 1.
Branch B: the brief is thin or the user names a project. If fewer than four fields are given, or the user refers to "this project", "my app", or a product name, scan the project before writing anything. Read files first, then present what you found.
WRONG (never do this in either branch):
Welcome to Brand Naming! I need a brief to get started. What are you naming? Please share: - What it is ... - Industry/category ... - Target audience ...
Scan procedure for Branch B (execute silently before any output):
- Read project files with the file reading and search tools -- do NOT skip this step:
- README.md, CLAUDE.md, package.json, pyproject.toml, Cargo.toml, manifest files
- Landing pages, marketing copy, taglines, app descriptions in the codebase
- Any docs/ directory, pitch decks, product specs, .planning/ directory
- Project structure, tech stack, and existing branding assets
- Also check the user's message and conversation history for context about what they're naming
What ships with it
1 file 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.
- 16d ago Changed · +4 lines 4ba885bbf168
- 1mo ago Changed · +21 lines 4855e6820419
- 1mo ago First seen · 297 lines · 81 tokens per session scan A 77ffcd96a259
brand-naming is a skill published in the GitHub repository acaprino/daodan (9 stars, last pushed today), licensed MIT. It adds 81 tokens to every session and 5,253 once invoked, about $0.0003 per session on Opus 5.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-09-05.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…