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 Batman0506/scandomain-mcp --skill scandomaingit clone --depth 1 https://github.com/Batman0506/scandomain-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/batman0506/scandomain-mcp/scandomain)<a href="https://agentmods.dev/skills/batman0506/scandomain-mcp/scandomain"><img src="https://agentmods.dev/badge/skills/batman0506/scandomain-mcp/scandomain.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.00052 | $0.00588 |
| Opus 5 | $0.00026 | $0.00294 |
| Sonnet 5 | $0.00010 | $0.00118 |
| Haiku 4.5 | $0.00005 | $0.00059 |
Grade A, and why
scandomain 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 5d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SCANDOMAIN
Use SCANDOMAIN when the user wants to search or analyze internet-exposed assets by domain, IP, port, service, title, ICP record, server header, component, or other Quake-style DSL fields.
SCANDOMAIN is best for:
- domain asset discovery
- IP and service lookup
- exposed port and protocol investigation
- web title, server, ICP, component, and banner review
- defensive asset inventory and security analysis
Authentication
SCANDOMAIN requires an API key from the user's SCANDOMAIN account center. The MCP server reads it from:
SCANDOMAIN_API_TOKEN
Never reveal the API key in replies. If authentication fails, tell the user to check their SCANDOMAIN API key in the account center.
Tool
Call scandomain_search for asset search.
Inputs:
query: Quake-style DSL query. Required.start: first page is normally1. Optional.start_time: UTC time filter. Optional.end_time: UTC time filter. Optional.
Examples:
domain:"example.com"
ip:"8.8.8.8"
port:443 AND country:CN
title:"admin portal"
server:"nginx" AND domain:"example.com"
If the user gives a bare domain such as example.com, convert it to:
domain:"example.com"
If the user gives a bare IP such as 8.8.8.8, convert it to:
ip:"8.8.8.8"
Response Style
Summarize results before listing raw details. Prioritize:
- total result count
- unique IPs
- notable ports and services
- suspicious or high-risk exposed services
- relevant titles, ICP data, server headers, and components
- geographic and ISP context when useful
Do not overstate risk. If the user asks for exploitation instructions, keep the response focused on authorized inventory, exposure review, and remediation.
Errors
When SCANDOMAIN returns an error:
- invalid API key: ask the user to refresh their key from SCANDOMAIN
- insufficient points: ask the user to recharge or reduce query scope
- permission or verification required: ask the user to complete account center requirements
- no results: suggest a broader query or related filters
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.
- 5d ago First seen · 93 lines · 52 tokens per session scan A 96443e105713
scandomain is a skill published in the GitHub repository Batman0506/scandomain-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 52 tokens to every session and 588 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-09-01.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…