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 commands/reolink/reolink-cli/statusgit clone --depth 1 https://github.com/reolink/reolink-cliWhat 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.00018 | $0.00120 |
| Opus 5 | $0.00009 | $0.00060 |
| Sonnet 5 | $0.00004 | $0.00024 |
| Haiku 4.5 | $0.00002 | $0.00012 |
Grade A, and why
status 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
Run reolink-cli status --output text and copy the full stdout into your reply as a fenced code block so the user can read it without having to expand a collapsed tool-output panel. Do not reinterpret, summarize, or add commentary above the dashboard — it's already formatted for human reading.
If the user passed an alias as $ARGUMENTS, run reolink-cli --alias $ARGUMENTS status --output text instead so recent events get included.
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 First seen · 8 lines · 18 tokens per session scan A ec0728b253e0
status is a command published in the GitHub repository reolink/reolink-cli (93 stars, last pushed 5d ago), licensed Apache-2.0. It adds 18 tokens to every session and 120 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.
Other commands, from other repositories
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.
add-ha-entity
Step-by-step guide to add a new Home Assistant entity with MQTT auto-discovery.
flash-size
Analyze firmware binary size and partition layout in detail.
observe
部屋を能動的に観察する。3つの基本ブロックを自由に選びながらループし、受動的なスナップショットではなく発見のある観察を行う。.
eol-report
EOL/EOS risk report — devices, OS versions, and firmware approaching or past end-of-life/end-of-support, prioritized by criticality.
rvcsi-calibrate
Learn a v0 per-subcarrier baseline (mean amplitude) from a .rvcsi capture.