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/cache-cleangit 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.00010 | $0.00253 |
| Opus 5 | $0.00005 | $0.00127 |
| Sonnet 5 | $0.00002 | $0.00051 |
| Haiku 4.5 | $0.00001 | $0.00025 |
Grade A, and why
cache-clean 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 2d 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
Clean old cache entries (snapshots, TTS PCM clips, etc.). The cache lives in the
platform cache directory — ~/.cache/reolink-cli/ on Linux,
~/Library/Caches/reolink-cli/ on macOS, %LOCALAPPDATA%\reolink-cli\cache\ on
Windows. Run reolink-cli cache status to see the resolved path rather than
assuming one.
Step 1 — preview (dry-run, always first):
Run reolink-cli cache clean --output json with any extra arguments in $ARGUMENTS (default retention is 7 d if none given). Show the candidate list with file count, total bytes, and the oldest file's age. Do NOT proceed to deletion yet.
Step 2 — confirm:
Ask the user to confirm deletion. Only if they explicitly say yes, proceed.
Step 3 — apply:
Re-run with --apply appended and show the deleted file count + freed bytes.
Never --apply without a confirmed dry-run output above it.
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.
- 2d ago First seen · 25 lines · 10 tokens per session scan A 54a099e584ed
cache-clean is a command published in the GitHub repository reolink/reolink-cli (93 stars, last pushed 5d ago), licensed Apache-2.0. It adds 10 tokens to every session and 253 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.
issues
Triage/fix the GitHub issue backlog via branch + PR, with auto-merge on green CI for this session.
release
Cut a release: follow the ha-release skill's procedure end to end.
sync-public-docs
Sync public VitePress documentation (docs/) with code changes — run before release or periodically on feature branches.
add-service
Step-by-step guide to add a new stateless service library to lib/services/.
sync-docs
Sync all CLAUDE.md and README.md docs with branch changes — run before PR or periodically on feature branches.