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 PleasePrompto/domain-check-skill --skill domain-checkgit clone --depth 1 https://github.com/PleasePrompto/domain-check-skillWrote 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/pleaseprompto/domain-check-skill/domain-check)<a href="https://agentmods.dev/skills/pleaseprompto/domain-check-skill/domain-check"><img src="https://agentmods.dev/badge/skills/pleaseprompto/domain-check-skill/domain-check/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/pleaseprompto/domain-check-skill/domain-check"><img src="https://agentmods.dev/badge/skills/pleaseprompto/domain-check-skill/domain-check.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.00267 | $0.02663 |
| Opus 5 | $0.00133 | $0.01332 |
| Sonnet 5 | $0.00053 | $0.00533 |
| Haiku 4.5 | $0.00027 | $0.00266 |
Grade A, and why
domain-check scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
The entire skill runs on the **Python ≥ 3.11 standard library** (needed for `dict | None` syntax and `asyncio.to_thread`). Module imports used by the skill: `argparse, asyncio, dataclasses, datetime, hashlib, io, json, o How it starts
The opening of the file, as written. The whole thing — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
domain-check
Platform-independent domain checker. Answers the binary question Available / Taken with high confidence (100% when all sources agree) and, for taken domains, returns the most relevant details inline: SSL certificate, server IP, expiration date.
MANDATORY READ — ANY DOMAIN-NAMING REQUEST
As the very first action — before generating, recommending, suggesting, scoring, or curating ANY domain names — you MUST Read references/naming_guide.md in full. Non-skippable. One Read tool call, ~3,300 words.
This rule fires on all of these triggers, not just on suggest:
- "schlag mir Domains vor", "suggest domains", "give me domain ideas"
- "good name for X", "guter Name für X", "creative domain names"
- "what should I call X", "wie soll ich X nennen"
- "Domain-Tipps", "domain tips", "naming ideas"
- bare
suggestsubcommand invocations - any free-form follow-up where the user asks for a curated list of names
The guide is the single source of truth. The Python score_name() heuristics are a sanity helper, NOT a substitute for the guide. Skipping the guide produces generic voicebotify / cloudhub slop that doesn't match the user's actual project.
Workflow for any naming request:
Read references/naming_guide.md— non-skippable, before any candidate is written- Pick 2–3 patterns from the guide that fit the user's project (e.g. "AI phone bot" → Hybrid Neoclassic + Action-Verb + Made-up-Phonetic, NOT just
voicebot+ify) - Hand-curate a candidate list using the guide's brainstorming techniques (semantic web, mood board, free association, grandma test, 1AM bar test)
- Run
bulkto check availability —suggestoutput is only a starting point, never the final list - Apply the don't-list (no hyphens, no digit substitutions, no false friends, no typo-squat distance ≤1)
- Present 8–15 curated finalists with rationale + buy_links, not 200 raw heuristic outputs
Requirements
No dependencies. No venv. No pip/uv/pipx required.
What ships with it
11 files 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.
- references/naming_guide.md 23 KB
- scripts/_lib/__init__.py 0 B runs code
- scripts/_lib/auth_dns.py 6.9 KB runs code
- scripts/_lib/naming.py 13 KB runs code
- scripts/_lib/orchestrator.py 10 KB runs code
- scripts/_lib/presence.py 8.7 KB runs code
- scripts/_lib/rdap.py 5.7 KB runs code
- scripts/_lib/tld_classifier.py 1.4 KB runs code
- scripts/_lib/verdict.py 6.4 KB runs code
- scripts/_lib/whois_client.py 16 KB runs code
- scripts/domain_check.py 8.2 KB runs code
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 · 173 lines · 267 tokens per session scan A fd4fda7fa26a
domain-check is a skill published in the GitHub repository PleasePrompto/domain-check-skill (6 stars, last pushed yesterday), licensed MIT. It adds 267 tokens to every session and 2,663 once invoked, about $0.0013 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
datarobot-agent-assist
Use when the user wants to design, build, code, simulate, or deploy an AI agent (not a predictive model) to DataRobot; mentions agentspec.md, dr-assist, datarobot-agent-assist, dress rehearsal, swarm simulation, or the DataRobot agent template; wants to scaffold a LangGraph, CrewAI, LlamaIndex, NAT, or Base agent…
datarobot-agent-assist-build
Use when the user wants to design, build, code, or deploy an AI agent on DataRobot; mentions agentspec.md, dress rehearsal, the DataRobot agent template, LangGraph, CrewAI, LlamaIndex, NAT, Base agents, MCP servers, backend APIs, custom frontends, or the DataRobot CLI.
datarobot-workload-api
Use when the user wants to create, configure, scale, debug, observe, or roll out container workloads on DataRobot's Workload API. Triggers include: deploying a container as a managed service, listing/starting/stopping workloads, changing replica counts or autoscaling, picking CPU/GPU compute bundles, injecting…
datarobot-predictions
Tools and guidance for making predictions with DataRobot deployments, including real-time predictions, batch scoring, prediction dataset generation, and prediction explanations (SHAP/XEMP). Use when making predictions, running batch scoring, generating prediction datasets, or explaining individual predictions from a…
datarobot-model-explainability
Tools and guidance for model explainability, prediction explanations, feature impact analysis, SHAP values, SHAP distributions, anomaly assessment, and model diagnostics. Use when analyzing model explanations, feature impact, SHAP values, SHAP distributions, anomaly assessment, or diagnosing model behavior.
datarobot-model-training
Comprehensive guidance for training models in DataRobot, including project creation, AutoML configuration, feature engineering, and model selection. Use when training models, creating AutoML projects, or selecting models in DataRobot.