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 kemalabuteliyte/domain-whois-mcp --skill domain-monitorgit clone --depth 1 https://github.com/kemalabuteliyte/domain-whois-mcpWrote 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/kemalabuteliyte/domain-whois-mcp/domain-monitor)<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.
<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>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.00065 | $0.00482 |
| Opus 5 | $0.00032 | $0.00241 |
| Sonnet 5 | $0.00013 | $0.00096 |
| Haiku 4.5 | $0.00006 | $0.00048 |
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.
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
- Call
rdap_lookupfirst (structured dates). Fall back towhois_lookupif RDAP is unavailable for the TLD. - Extract the expiration date and status codes.
- 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
- 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 ownerpendingDelete— final 5 days before dropautoRenewPeriod— auto-renewed; don't count on it dropping
Realistic assessment rules
- High-value
.comdomains 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.
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.
- 11d ago First seen · 43 lines · 65 tokens per session scan A 607efc8cf1cf
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.
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.
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.
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.
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.
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…
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.