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 agentmods add instructions/reolink/reolink-cli/agents-mdgit 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/instructions/reolink/reolink-cli/agents-md)<a href="https://agentmods.dev/instructions/reolink/reolink-cli/agents-md"><img src="https://agentmods.dev/badge/instructions/reolink/reolink-cli/agents-md.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 | $0.03721 | $0.03721 |
| Opus 5 | $0.01861 | $0.01861 |
| Sonnet 5 | $0.00744 | $0.00744 |
| Haiku 4.5 | $0.00372 | $0.00372 |
Grade D, and why
reolink-cli AGENTS.md scanned grade D with 3 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 4d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
| Linux (Debian/Ubuntu) | `sudo apt-get install -y ffmpeg` | Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -fsSL https://raw.githubusercontent.com/reolink/reolink-cli/main/install.sh | sh Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -fsSL https://raw.githubusercontent.com/reolink/reolink-cli/main/install.sh | sh How it starts
The opening of the file, as written. The whole thing — 275 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Setup — reolink-cli
Read this when an AI agent first encounters the plugin. Your job is to confirm the install, then operate cameras via the skill.
If the binaries are not on disk yet, the one-line installer fetches them and verifies the download against the checksum committed to this repository:
curl -fsSL https://raw.githubusercontent.com/reolink/reolink-cli/main/install.sh | sh
What you (the AI) should do, in order:
- Part 1 — Verify the install (binaries on PATH, gateway reachable).
- Part 2 — Confirm the skill is loaded for your agent surface.
- Part 3–4 — Start the gateway and (first time only) add a camera.
- Part 5 — Echo installed versions back to the user.
If any step fails, do not silently continue — see Part 6 — Troubleshooting and surface the remedy.
Part 1 — Verify CLI install
Both binaries should be at ~/.local/bin/ (or %USERPROFILE%\.local\bin\ on Windows).
reolink-cli --version
command -v reolink-gateway
If command not found, the install prefix isn't on PATH:
# Unix
export PATH="$HOME/.local/bin:$PATH"
# Windows PowerShell
$env:PATH += ";$HOME\.local\bin"
To upgrade, run reolink-cli self-update (macOS and Linux). It checks the
latest release, replaces both binaries in place, and is a no-op when already
current. On Windows it exits with the download link instead: the archive is a
.zip and a running .exe cannot be replaced in place, so upgrade there by
extracting the new archive and running install.ps1.
Re-running the one-line installer is an equivalent upgrade path on any platform, and is idempotent — it overwrites both binaries in place.
Part 2 — Confirm the skill is loaded
The plugin tree (SKILL.md, slash commands, skill references) is already on disk after the install. How your agent surface sees it depends on the agent:
| Agent | Skill path |
|---|---|
| Claude Code | ~/.claude/plugins/cache/reolink-cli/reolink-cli/<version>/ (auto-loaded by /plugin install) |
| Codex | Symlinked into ~/.agents/skills/reolink-cli by setup-codex on first install |
| Gemini CLI | GEMINI.md next to this file is treated as agent context |
| Cursor / Windsurf | .cursor-plugin/ next to this file is auto-detected on workspace open |
| Other | Read skills/reolink-cli/SKILL.md next to this file as a system rule |
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.
- 4d ago First seen · 275 lines · 3,721 tokens per session scan D 357d54915181
reolink-cli AGENTS.md is an instructions file published in the GitHub repository reolink/reolink-cli (93 stars, last pushed 6d ago), licensed Apache-2.0. It adds 3,721 tokens to every session, about $0.0186 per session on Opus 5. A static security scan graded it D with 3 findings (asks for root, downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
HomeAssistant-Tapo-Control AGENTS.md
Instructions for JurajNyiri/HomeAssistant-Tapo-Control, covering agent instructions, required user agreement, repository rules and commits and prs.
HomeAssistant-Tapo-Control CLAUDE.md
Instructions for JurajNyiri/HomeAssistant-Tapo-Control: Follow AGENTS.md and CONTRIBUTING.md before working in this repository.
robsonfelix-hass-addons CLAUDE.md
Instructions for robsonfelix/robsonfelix-hass-addons, covering claude code instructions, before every commit, added/changed/fixed, project structure and version bumping.
advanced-homeassistant-mcp copilot-instructions.md
Instructions for jango-blockchained/advanced-homeassistant-mcp, covering ai agent instructions for homeassistant-mcp, 1. architecture & core concepts, key components, 2. developer workflow & commands and building the project.
hass-mcp CLAUDE.md
Instructions for czechbol/hass-mcp, covering claude.md, what this is, commands, architecture and adding a tool.
reolink-mcp CLAUDE.md
Instructions for ed-dryha/reolink-mcp, covering project, constraints, technology stack, verdict on the seeded stack and recommended stack.