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/update)<a href="https://agentmods.dev/commands/reolink/reolink-cli/update"><img src="https://agentmods.dev/badge/commands/reolink/reolink-cli/update/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/update"><img src="https://agentmods.dev/badge/commands/reolink/reolink-cli/update.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.00015 | $0.00397 |
| Opus 5.5 | $0.00006 | $0.00159 |
| Sonnet 5.5 | $0.00003 | $0.00079 |
| Haiku 4.5 | $0.00002 | $0.00040 |
Grade A, and why
update 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.
What it actually says
Container deployments (Docker-backed entry or REOLINK_CONTAINER): update the selected published image version and recreate the Compose service with its existing data volume. Use the container recipe in the repository distribution guide; report the old/new container CLI versions. Do not run self-update or kill host gateways for a container deployment. Stop here after the container workflow; the steps below are for native installations.
Upgrade the installed binaries to the latest release.
-
Run the built-in updater:
reolink-cli self-update --yesIt checks the latest GitHub release, compares against the installed version, and — if newer — downloads the archive for this platform and replaces both
reolink-cliandreolink-gatewayin place. If already current it printsalready up to dateand does nothing. Stop a running gateway first (pkill reolink-gatewayon Unix;Stop-Process -Name reolink-gatewayon Windows) so the binary file isn't locked. -
Report the pre- and post-upgrade version (
reolink-cli --version).
Notes:
self-updatetargets the public GitHub release. SetREOLINK_UPDATE_REPO(owner/repo) to point at a fork/mirror, orGITHUB_TOKENfor a private repo.- Windows self-update is not wired (it fetches
.tar.gz); on Windows, download the latest...-windows-x86_64.zipfrom the Releases page and extractbin\over the installed copy, or re-runinstall.ps1from a fresh tarball. - Re-run
reolink-cli completions …after upgrading if you use shell completion.
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.
- 3d ago Changed · +2 lines a612dcedfe9f
- 2mo ago First seen · 29 lines · 15 tokens per session scan A 651d7508bc7c
update is a command published in the GitHub repository reolink/reolink-cli (118 stars, last pushed 3d ago), licensed Apache-2.0. It adds 15 tokens to every session and 397 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.
update compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| updatereolink/reolink-cli | Command | 118 | 3d ago | Apache-2.0 | A | 15 | Claude Code |
| review-branchdamusix/atomic-claude | Command | 115 | 4d ago | MIT | A | 35 | Claude Code |
| securityajitpratap0/GoSQLX | Command | 124 | 2d ago | Apache-2.0 | A | 21 | Claude Code |
| commitechoVic/blade-code | Command | 181 | 24d ago | MIT | A | 8 | Claude Code |
| modernize-transformfuxicodex/Fuxi | Command | 3.2k | 17d ago | none | A | 17 | Claude Code |
| react-nativegetsentry/toolkit | Command | 957 | yesterday | none | A | 0 | Claude Code |
| amp-registeragentmessaging/claude-plugin | Command | 5 | 5d ago | Apache-2.0 | A | 0 | Claude Code |