scan

A command that searches the local network for Reolink devices using a two-second UDP broadcast, a local-network discovery message.

In plain words
What is it for?
Use it to list discovered devices with their host addresses, unique IDs, and names. Devices on another subnet or VLAN will not appear.
Why use it?
It quickly shows which cameras are visible on the current network segment, while making clear when none are found.

Command

Install

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.

agentmods
npx agentmods add commands/reolink/reolink-cli/scan
Clone the repo
git clone --depth 1 https://github.com/reolink/reolink-cli
Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 130 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00017 $0.00130
Opus 5 $0.00009 $0.00065
Sonnet 5 $0.00003 $0.00026
Haiku 4.5 $0.00002 $0.00013

Measured 3d ago against content hash 56f0f0460f29, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

scan 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 3d 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.

commands/scan.md · 14 lines

What it actually says

Run reolink-cli discover --output json and parse the data.devices[] array. Report each device as one line:

<host>  uid=<uid>  "<name-from-scopes>"

If no devices found, say so plainly and mention that UDP broadcast doesn't cross subnets — if the user's cameras are on another VLAN they will not show up here.

Do not re-scan with longer timeouts unless the user explicitly asks. The default 2 s already catches everything on the local broadcast domain.

Changes

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.

  1. 3d ago First seen · 14 lines · 17 tokens per session scan A 56f0f0460f29

Subscribe to this mod's changes

scan is a command published in the GitHub repository reolink/reolink-cli (93 stars, last pushed 5d ago), licensed Apache-2.0. It adds 17 tokens to every session and 130 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.