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.
git clone --depth 1 https://github.com/luongnv89/skillsWrote 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/agents/luongnv89/skills/domain-checker)<a href="https://agentmods.dev/agents/luongnv89/skills/domain-checker"><img src="https://agentmods.dev/badge/agents/luongnv89/skills/domain-checker.svg" alt="Measured on agentmods" 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.00022 | $0.01186 |
| Opus 5 | $0.00011 | $0.00593 |
| Sonnet 5 | $0.00004 | $0.00237 |
| Haiku 4.5 | $0.00002 | $0.00119 |
Grade A, and why
domain-checker 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Domain Checker Agent
Check domain availability across .com, .io, .app, .co and regional TLDs, returning registration status and active site info.
Input
{
"name": "myproductname",
"regional_tlds": ["eu", "fr"]
}
Process
Check each TLD independently:
Primary TLDs
- .com - Highest priority, most sought-after
- .io - Popular for tech startups
- .app - Google registry, modern and trustworthy
- .co - Alternative to .com, increasingly popular
Regional TLDs
.eu- European Union.fr- France (if relevant)- Other regional codes as provided in input
For each TLD, search:
- Query 1:
"[NAME].[TLD]" domain registry status - Query 2:
site:[NAME].[TLD]to check for active site - Query 3: Domain registrar availability (GoDaddy, Namecheap, etc.)
Status Determination
- Available: No active site, domain not registered
- Parked: Domain exists but no active site (parking page, "for sale")
- Active: Domain registered and in use
Output
Return JSON with this structure:
{
"name": "myproductname",
"timestamp": "2026-03-24T10:30:00Z",
"domain_status": {
"com": {
"status": "available|parked|active|error",
"tld": ".com",
"full_domain": "myproductname.com",
"site_found": false,
"site_description": null,
"site_industry": null,
"registrar": "registrar name or null",
"expiry": "2026-04-15 or null",
"confidence": "high|medium|low"
},
"io": {
"status": "available|parked|active|error",
"tld": ".io",
"full_domain": "myproductname.io",
"site_found": false,
"site_description": null,
"site_industry": null,
"registrar": "registrar name or null",
"expiry": "2026-04-15 or null",
"confidence": "high|medium|low"
},
"app": {
"status": "available|parked|active|error",
"tld": ".app",
"full_domain": "myproductname.app",
"site_found": false,
"site_description": null,
"site_industry": null,
"registrar": "registrar name or null",
"expiry": "2026-04-15 or null",
"confidence": "high|medium|low"
},
"co": {
"status": "available|parked|active|error",
"tld": ".co",
"full_domain": "myproductname.co",
"site_found": false,
"site_description": null,
"site_industry": null,
"registrar": "registrar name or null",
"expiry": "2026-04-15 or null",
"confidence": "high|medium|low"
},
"eu": {
"status": "available|parked|active|error",
"tld": ".eu",
"full_domain": "myproductname.eu",
"site_found": false,
"site_description": null,
"site_industry": null,
"registrar": "registrar name or null",
"expiry": "2026-04-15 or null",
"confidence": "high|medium|low"
},
"fr": {
"status": "available|parked|active|error",
"tld": ".fr",
"full_domain": "myproductname.fr",
"site_found": false,
"site_description": null,
"site_industry": null,
"registrar": "registrar name or null",
"expiry": "2026-04-15 or null",
"confidence": "high|medium|low"
}
},
"summary": {
"com_status": "available|parked|active",
"com_critical": true,
"all_primary_available": false,
"primary_available": ["io", "app", "co"],
"primary_taken": ["com"],
"active_in_same_industry": false
},
"notes": "myproductname.com is active but parked. io, app, co available. Consider acquiring at least .io if .com unavailable."
}
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.
- 8d ago First seen · 152 lines · 22 tokens per session scan A 9d1e7f8bc91a
domain-checker is an agent published in the GitHub repository luongnv89/skills (123 stars, last pushed 3d ago), licensed MIT. It adds 22 tokens to every session and 1,186 once invoked, about $0.0001 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-30.
Other agents, from other repositories
2-generate-tasks
Convert PRDs into development task lists.
cf-reviewer-security
Security review specialist. Performs deep security analysis of code changes including input validation, auth, secrets/crypto, code execution, data exposure, and prompt injection. Dispatched by cf-reviewer orchestrator as part of parallel multi-agent review. Includes exploit scenarios for Critical findings. Traces data…
cf-reviewer-rules
Project rules compliance specialist. Checks code changes against AGENTS.md project rules. Only flags violations of rules with MUST/SHOULD/ALWAYS/NEVER language. Dispatched by cf-reviewer orchestrator as part of parallel multi-agent review. Skipped in QUICK review mode.
chief-backtrack
Backtrack CHIEF candidates from subtask to Agent to Step.
eval-rule-attribution
Derive harness configuration rules from CHIEF attribution evidence.
vision
Analyze images with task-aware visual reasoning.