namer

namer is a skill for Claude Code from wyattowalsh/agents. It costs 77 tokens per session (4,258 once invoked), scanned A, original, MIT.

A naming assistant for projects, products, companies, packages, and brands. It generates name ideas, checks domain and username availability, and ranks the results.

In plain words
What is it for?
Use it to name a new project or product, create variations of an existing name, compare candidates, and review saved naming sessions.
Why use it?
It reduces the manual work of brainstorming names and checking whether they are already in use.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: model in frontmatter; mentions subagents; mentions Codex.

Part of the agents plugin — 71 skills, 20 agents, 5 hooks shipped together

Good fit Use it to name a new project or product, create variations of an existing name, compare candidates, and review saved naming sessions.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/wyattowalsh/agents/namer
Install

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.

Any agent
npx skills add wyattowalsh/agents --skill namer
Clone the repo
git clone --depth 1 https://github.com/wyattowalsh/agents

Made for: Claude Code.

Or install agents, the plugin that ships this one along with the rest of its 71 skills, 20 agents, 5 hooks.

Wrote 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.

agentmods badge for namer

README.md
[![agentmods](https://agentmods.dev/badge/skills/wyattowalsh/agents/namer/github.svg)](https://agentmods.dev/skills/wyattowalsh/agents/namer)
Your own site
<a href="https://agentmods.dev/skills/wyattowalsh/agents/namer"><img src="https://agentmods.dev/badge/skills/wyattowalsh/agents/namer/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.

agentmods 80×15 button for namer

Your own site · 80×15
<a href="https://agentmods.dev/skills/wyattowalsh/agents/namer"><img src="https://agentmods.dev/badge/skills/wyattowalsh/agents/namer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 77 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,258 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00077 $0.04258
Opus 5.5 $0.00031 $0.01703
Sonnet 5.5 $0.00015 $0.00852
Haiku 4.5 $0.00008 $0.00426

Measured 1mo ago against content hash 9c564fed6a55, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

namer 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 1mo ago.

The scan reads SKILL.md. This mod also ships 12 executable files (scripts/asset_toolkit/__init__.py, scripts/asset_toolkit/_shared.py, scripts/asset_toolkit/common.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/namer/SKILL.md · 297 lines

How it starts

The opening of the file, as written. The whole thing — 297 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Namer

Generate, evaluate, and validate names across linguistic, technical, and platform dimensions. Produces ranked options with availability matrices and actionable next steps.

Not for domain registration, branding strategy, or logo design. Not for reviewing naming conventions in existing code.

Dispatch

$ARGUMENTS Action
<thing to name> (with optional flags) Name — full pipeline: brief → generate → filter → check → score → rank
check <name> [name2...] Check — availability audit only (skip generation)
expand <name> Expand — generate variations/modifications of an existing name
compare <name1> vs <name2> [vs...] Compare — side-by-side scoring of specific names
resume [# or keyword] Resume — load prior naming session
list List — show saved naming sessions
preferences Preferences — show accumulated naming profile and memory stats
Empty Gallery — show examples + "what are you naming?" prompt

Gallery (Empty Arguments)

# Context Example
1 CLI Tool "I'm building a terminal file manager in Rust"
2 SaaS Product "Developer productivity tool for code review"
3 OSS Library "Python library for data validation"
4 Startup "AI-powered hiring platform"
5 Side Project "Weekend project — a bookmark manager"
6 Brand "Design agency specializing in developer tools"

Read the full file on GitHub · 297 lines

Changes

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.

  1. 1mo ago First seen · 297 lines · 77 tokens per session scan A 9c564fed6a55

Subscribe to this mod's changes

namer is a skill published in the GitHub repository wyattowalsh/agents (5 stars, last pushed 1mo ago), licensed MIT. It adds 77 tokens to every session and 4,258 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-03.

Related

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…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens