72
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill aidotnet/moyucode --skill port-scanner- SKILL.md868 B
Overview
This skill scans network ports to check availability, detect running services, and identify open TCP endpoints. It provides single-port checks, ranged scans, common-port presets, and availability queries to help troubleshoot connectivity and surface potential security issues.
How this skill works
The scanner attempts TCP connections to target hosts and ports, reporting success, timeout, or refusal for each attempt. It supports scanning a single port, a numeric range, or a curated set of common ports, and can flag ports that appear available for binding. Results include basic service detection by observing banner responses when available.
When to use it
- Verify a single service is reachable on a host and port before deploying or testing.
- Audit a host for unexpectedly open ports that may expose services.
- Troubleshoot connectivity issues during development or CI checks.
- Quickly check a port range when configuring firewalls or network rules.
- Confirm whether a port is free on a machine before starting a server process.
Best practices
- Run scans from a network location that reflects the client perspective (local, VPN, or public) to get meaningful results.
- Respect scanning policies and obtain permission before probing hosts you do not own.
- Combine results with firewall rules and service logs to pinpoint root causes of failures.
- Use conservative timeouts and rate limits to avoid triggering intrusion detection systems.
- When possible, corroborate banner-based detection with authenticated checks or service-specific probes.
Example use cases
- Check whether a web server is listening on port 8080 before starting a CI smoke test.
- Scan 192.168.1.1 for ports 80–443 after a network change to validate firewall rules.
- Run a common-port scan against an instance to quickly identify active services like SSH or HTTP.
- Confirm that port 3000 is available on a development machine before launching a local app.
- Perform a quick security check on a newly provisioned VM to list exposed TCP services.
FAQ
Yes, it focuses on TCP connection attempts and banner observation; UDP probing is not included.
Will scanning a host without permission cause problems?
Scanning can trigger security alerts or violate policies—always get authorization before scanning hosts you do not control.