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/reolink/reolink-cliWrote 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/commands/reolink/reolink-cli/devices)<a href="https://agentmods.dev/commands/reolink/reolink-cli/devices"><img src="https://agentmods.dev/badge/commands/reolink/reolink-cli/devices/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/reolink/reolink-cli/devices"><img src="https://agentmods.dev/badge/commands/reolink/reolink-cli/devices.svg" alt="Reviewed on agentmods" width="80" 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.00019 | $0.00120 |
| Opus 5.5 | $0.00008 | $0.00048 |
| Sonnet 5.5 | $0.00004 | $0.00024 |
| Haiku 4.5 | $0.00002 | $0.00012 |
Grade A, and why
devices 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 1mo 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.
What it actually says
Run reolink-cli device list --output json and print each alias on one line as:
<alias> <host|uid> tags=[<tags>] <description>
Omit the password/hasPassword column (the CLI already masks it; don't repeat what's sensitive). If the alias list is empty, tell the user to register one with reolink-cli device add <alias> --host <ip> --user admin.
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.
- 1mo ago First seen · 12 lines · 19 tokens per session scan A 82ef1c1b2d5a
devices is a command published in the GitHub repository reolink/reolink-cli (117 stars, last pushed 14d ago), licensed Apache-2.0. It adds 19 tokens to every session and 120 once invoked, about $0.0001 per session on Opus 5.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 commands, from other repositories
unifly-status
Read-only health check of UniFi infrastructure, including devices and alerts.
aurora
Aurora - independent community smart home orchestrator. Routes any smart home request to the right specialist skill and recommends the correct Claude model. Use this as your starting point for Home Assistant, ESPHome, Node-RED, or any IoT automation task.
maker-setup
Onboard a Code-with-FuXi Makers Cardputer — fetch the build-with-fuxi repo, flash firmware, and install the FuXi Buddy apps.
maker-setup
Onboard a Code-with-Gemini Makers Cardputer — fetch the build-with-gemini repo, flash firmware, and install the Gemini Buddy apps.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.