domain-monitor

domain-monitor is a skill for Claude Code from kemalabuteliyte/domain-whois-mcp. It costs 65 tokens per session (482 once invoked), scanned A, original, MIT.

A guide for choosing a domain ending, called a top-level domain or TLD, such as .com, .dev, or .ai. It considers the project's audience, category, brand fit, and TLD infrastructure.

In plain words
What is it for?
Use it when comparing endings for products such as developer tools, AI products, SaaS applications, APIs, open-source projects, games, or local businesses.
Why use it?
It helps resolve uncertainty when deciding which domain ending suits a project. It combines factual information about TLD support with category-based recommendations.

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 when comparing endings for products such as developer tools, AI products, SaaS applications, APIs, open-source projects, games, or local businesses.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/kemalabuteliyte/domain-whois-mcp/domain-monitor
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 domain-monitor
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 domain-monitor

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/kemalabuteliyte/domain-whois-mcp/domain-monitor"><img src="https://agentmods.dev/badge/skills/kemalabuteliyte/domain-whois-mcp/domain-monitor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 65 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 482 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.00065 $0.00482
Opus 5 $0.00032 $0.00241
Sonnet 5 $0.00013 $0.00096
Haiku 4.5 $0.00006 $0.00048

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

Security

Grade A, and why

domain-monitor 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/domain-monitor/SKILL.md · 43 lines

What it actually says

Domain Monitor

Detect how soon a domain will expire and report whether it's a realistic acquisition target.

When to Use

  • User asks when a specific domain expires
  • User wants to know if a domain is about to drop (potentially become available)
  • User says "I want example.com, can I get it?"
  • User is researching a competitor's domain portfolio

Workflow

  1. Call rdap_lookup first (structured dates). Fall back to whois_lookup if RDAP is unavailable for the TLD.
  2. Extract the expiration date and status codes.
  3. Classify:
    • > 180 days: not actionable — not worth watching yet
    • 90–180 days: distant — note it
    • 30–90 days: approaching — watch for renewal
    • 0–30 days: imminent — may drop if unrenewed
    • expired: check status codes like redemptionPeriod, pendingDelete — there's a ~75-day grace window before the domain becomes generally registrable
  4. Report: domain, expiration date, days-to-expiry, current registrar, status codes, realistic assessment.

Status codes to highlight

  • clientTransferProhibited / serverTransferProhibited — owner or registry locked transfers (normal for active domains)
  • redemptionPeriod — expired but in grace; can still be redeemed by the old owner
  • pendingDelete — final 5 days before drop
  • autoRenewPeriod — auto-renewed; don't count on it dropping

Realistic assessment rules

  • High-value .com domains rarely drop — someone is usually watching.
  • If the domain has DNSSEC set up, it's actively maintained — low drop probability.
  • If nameservers point to a parking service, it's often owned by a domainer — will be sold, not dropped.

Be honest: most "expiring" domains get renewed at the last minute.

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 · 43 lines · 65 tokens per session scan A 607efc8cf1cf

Subscribe to this mod's changes

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