project-name-finder

project-name-finder is a skill for Claude Code from kemalabuteliyte/domain-whois-mcp. It costs 106 tokens per session (856 once invoked), scanned A, original, MIT.

A naming helper for new projects, products, and startups that suggests names and checks whether matching web addresses are available across different endings such as .com and .dev.

In plain words
What is it for?
Use it to name a project, product, company, or brand and check possible web addresses at the same time.
Why use it?
It reduces the back-and-forth between inventing a name and discovering that its web address is already taken. It also helps narrow many ideas into a ranked shortlist.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the domain-whois-mcp plugin — 4 skills, 4 commands, 1 agent, 1 MCP server shipped together

Good fit Use it to name a project, product, company, or brand and check possible web addresses at the same time.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/kemalabuteliyte/domain-whois-mcp/project-name-finder
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 kemalabuteliyte/domain-whois-mcp --skill project-name-finder
Clone the repo
git clone --depth 1 https://github.com/kemalabuteliyte/domain-whois-mcp

Made for: Claude Code.

Or install domain-whois-mcp, the plugin that ships this one along with the rest of its 4 skills, 4 commands, 1 agent, 1 MCP server.

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 project-name-finder

README.md
[![agentmods](https://agentmods.dev/badge/skills/kemalabuteliyte/domain-whois-mcp/project-name-finder/github.svg)](https://agentmods.dev/skills/kemalabuteliyte/domain-whois-mcp/project-name-finder)
Your own site
<a href="https://agentmods.dev/skills/kemalabuteliyte/domain-whois-mcp/project-name-finder"><img src="https://agentmods.dev/badge/skills/kemalabuteliyte/domain-whois-mcp/project-name-finder/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 project-name-finder

Your own site · 80×15
<a href="https://agentmods.dev/skills/kemalabuteliyte/domain-whois-mcp/project-name-finder"><img src="https://agentmods.dev/badge/skills/kemalabuteliyte/domain-whois-mcp/project-name-finder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 106 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 856 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.00106 $0.00856
Opus 5 $0.00053 $0.00428
Sonnet 5 $0.00021 $0.00171
Haiku 4.5 $0.00011 $0.00086

Measured 11d ago against content hash cd863292c637, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

project-name-finder 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 11d 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.

skills/project-name-finder/SKILL.md · 76 lines

How it starts

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

Project Name Finder

Help the user find an available domain name for a new project. The value is the pairing of creative brainstorming + live bulk availability checks — names that sound great but are taken add no value.

Workflow

1. Clarify (one question, not a form)

Ask exactly one short question if the concept isn't clear:

  • What does the project do, and who's it for?

Skip if the user already gave you enough (e.g. "AI invoicing for freelancers").

2. Brainstorm candidates

Generate 15–30 candidate names. Heuristics:

  • Short (≤ 10 chars preferred, absolute max 14)
  • Pronounceable — read them aloud mentally
  • No hyphens, no numbers, no digit-letter substitution (0 for o)
  • Avoid obvious trademark collisions (don't prefix/suffix "Google", "Apple", etc.)
  • Mix styles: real words, portmanteaus, made-up, latin/greek roots, verbs
  • Avoid over-used AI-era suffixes unless it really fits (-ify, -ly, AI, GPT)

3. Fan out across TLDs

Default TLD set: .com .io .dev .ai .app .co. Add .so .xyz if the user is open to alternative TLDs, or .sh .fm .gg for specific verticals.

Build the full list as name.tld pairs and call:

bulk_domain_check({
  domains: [ /* N candidates × M tlds */ ],
  concurrency: 5
})

If you have > 50 domain+TLD combinations, split into batches of 50.

4. Rank

Sort descending by this composite score:

  1. .com available → +10
  2. .io or .dev or .ai available → +3 each
  3. Length bonus: 10 - name_length (floor 0)
  4. Penalty: -5 if contains hyphen, -3 if ≥ 12 chars
  5. Bonus: +2 if available on 3+ of the default TLDs

5. Return the shortlist

Give the user a table of the top 5:

Name Available on Notes
... .com, .io, .dev short, made-up, easy to say

Follow up with: "Want me to pull full WHOIS / RDAP for any of the taken ones to see if they're expiring soon?"

Example call

User: "I'm starting an AI invoicing SaaS for freelancers, help me find a name."

Read the full file on GitHub · 76 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. 11d ago First seen · 76 lines · 106 tokens per session scan A cd863292c637

Subscribe to this mod's changes

project-name-finder is a skill published in the GitHub repository kemalabuteliyte/domain-whois-mcp (0 stars, last pushed 4mo ago), licensed MIT. It adds 106 tokens to every session and 856 once invoked, about $0.0005 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.

Related

Other skills, from other repositories

design-mcp-server

Design the tool surface, resources, and service layer for a new MCP server. Use when starting a new server, planning a major feature expansion, or when the user describes a domain/API they want to expose via MCP. Produces a design doc at docs/design.md that drives implementation.

cyanheads/whois-mcp-server · 62 tokens

add-tool

Scaffold a new MCP tool definition. Use when the user asks to add a tool, create a new tool, or implement a new capability for the server.

cyanheads/whois-mcp-server · 35 tokens

api-context

Canonical reference for the unified Context object passed to every tool and resource handler in @cyanheads/mcp-ts-core. Covers the full interface, its RequestContext base, all sub-APIs (ctx.log, ctx.state, ctx.requestInput, ctx.inputs, ctx.enrich, ctx.content), and when to use each.

cyanheads/whois-mcp-server · 79 tokens

api-linter

MCP definition linter rules reference. Use when bun run lint:mcp or bun run devcheck reports a lint error or warning (format-parity, schema-is-object, name-format, server-json-, etc.) and you need to understand the rule, its severity, and how to fix it. Every rule ID the linter emits has an entry in this doc.

cyanheads/whois-mcp-server · 86 tokens

api-canvas

DataCanvas primitive reference — a Tier 3 SQL/analytical workspace for tabular MCP servers, backed by DuckDB. Use when registering tables from upstream APIs, running ad-hoc SQL across them, and exporting results. Covers the acquire → register → query → export flow, per-table TTL, the token-sharing pattern for…

cyanheads/whois-mcp-server · 85 tokens

api-errors

McpError constructor, JsonRpcErrorCode reference, and error handling patterns for @cyanheads/mcp-ts-core. Use when looking up error codes, understanding where errors should be thrown vs. caught, or using ErrorHandler.tryCatch in services.

cyanheads/whois-mcp-server · 54 tokens