agentleFS
Sign inStart free
BrownFineSecurityBrownFineSecurity/iothackbot/skills/wsdiscovery/SKILL.md

wsdiscovery

Skill847 starsChanged 5 months agoMITView on GitHub

WS-Discovery protocol scanner for discovering and enumerating ONVIF cameras and IoT devices on the network. Use when you need to discover ONVIF devices, cameras, or WS-Discovery enabled equipment on a network.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When the user asks to discover ONVIF devices, find network cameras, or scan for WS-Discovery devices:

    line 16
  2. Distinctive:

    Ask for the target hostname or IP address

    line 19
  3. Very specific:

    Use the wsdiscovery command from the iothackbot bin directory

    line 24

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Wsdiscovery - WS-Discovery Protocol Scanner

You are helping the user discover and enumerate devices using the WS-Discovery protocol (commonly used by ONVIF cameras and IoT devices) using the wsdiscovery tool.

Tool Overview

Wsdiscovery implements the WS-Discovery protocol to discover network devices that support this standard. It's particularly useful for finding ONVIF cameras, network video recorders (NVRs), and other IoT devices that advertise themselves via WS-Discovery.

Instructions

When the user asks to discover ONVIF devices, find network cameras, or scan for WS-Discovery devices:

  1. Understand the target:
    • Ask for the target hostname or IP address
    • Determine if they want verbose output (full XML responses)
    • Decide on output format
  2. Execute the scan:
    • Use the wsdiscovery command from the iothackbot bin directory
    • Basic usage: wsdiscovery <hostname_or_ip>
    • For verbose output: wsdiscovery <hostname_or_ip> -v
    • For JSON output: wsdiscovery <hostname_or_ip> --format json
  3. Output formats:
    • --format text (default): Human-readable colored output with device details
    • --format json: Machine-readable JSON
    • --format quiet: Minimal output

What It Discovers

The tool extracts and displays:

  • IP addresses and ports
  • Endpoint references (device UUIDs)
  • Device types
  • Manufacturer information
  • Device names and models
  • Hardware versions
  • Serial numbers
  • Firmware versions
  • Location information
  • Service endpoints (XAddrs) - URLs for device management
  • Metadata versions

Examples

Discover devices on a specific host:

wsdiscovery 192.168.1.100

Discover with full XML responses:

wsdiscovery 192.168.1.100 -v

Output device information as JSON:

wsdiscovery 192.168.1.100 --format json

Scan network broadcast address to find all devices:

wsdiscovery 239.255.255.250

Important Notes

  • WS-Discovery uses multicast/broadcast discovery
  • Devices must support the WS-Discovery protocol to be found
  • Common with ONVIF cameras, printers, and network media devices
  • Service endpoints (XAddrs) can be used with onvifscan for further testing
  • The tool parses ONVIF-specific scope information when available

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free