rclone_check

rclone_check is a command for Claude Code from olorehq/olore. It costs 10 tokens per session (1,444 once invoked), scanned A, original, MIT.

A file comparison command that checks whether files in a source and destination match by comparing their sizes and checksums. It only reports differences and does not change either location.

In plain words
What is it for?
Use it to validate backups, compare local and cloud folders, or produce reports of files that differ.
Why use it?
It helps verify a copy or synchronisation without risking changes to the files. It can reveal missing, extra, or altered files between two storage locations.

Command for Claude Code

Written for Claude Code: a Claude Code command (commands/*.md).

Good fit Use it to validate backups, compare local and cloud folders, or produce reports of files that differ.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/olorehq/olore/rclone_check
Install

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.

Clone the repo
git clone --depth 1 https://github.com/olorehq/olore

Made for: Claude Code.

Wrote 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.

agentmods badge for rclone_check

README.md
[![agentmods](https://agentmods.dev/badge/commands/olorehq/olore/rclone_check/github.svg)](https://agentmods.dev/commands/olorehq/olore/rclone_check)
Your own site
<a href="https://agentmods.dev/commands/olorehq/olore/rclone_check"><img src="https://agentmods.dev/badge/commands/olorehq/olore/rclone_check/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.

agentmods 80×15 button for rclone_check

Your own site · 80×15
<a href="https://agentmods.dev/commands/olorehq/olore/rclone_check"><img src="https://agentmods.dev/badge/commands/olorehq/olore/rclone_check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,444 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00010 $0.01444
Opus 5 $0.00005 $0.00722
Sonnet 5 $0.00002 $0.00289
Haiku 4.5 $0.00001 $0.00144

Measured 5d ago against content hash 72f1b15ac7fb, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

rclone_check 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 5d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

vault/packages/rclone/1.74.3/contents/commands/rclone_check.md · 133 lines

How it starts

The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.

rclone check

Checks the files in the source and destination match.

Synopsis

Checks the files in the source and destination match. It compares sizes and hashes (MD5 or SHA1) and logs a report of files that don't match. It doesn't alter the source or destination.

For the crypt remote there is a dedicated command, cryptcheck, that are able to check the checksums of the encrypted files.

If you supply the --size-only flag, it will only compare the sizes not the hashes as well. Use this for a quick check.

If you supply the --download flag, it will download the data from both remotes and check them against each other on the fly. This can be useful for remotes that don't support hashes or if you really want to check all the data.

If you supply the --checkfile HASH flag with a valid hash name, the source:path must point to a text file in the SUM format.

If you supply the --one-way flag, it will only check that files in the source match the files in the destination, not the other way around. This means that extra files in the destination that are not in the source will not be detected.

The --differ, --missing-on-dst, --missing-on-src, --match and --error flags write paths, one per line, to the file name (or stdout if it is -) supplied. What they write is described in the help below. For example --differ will write all paths which are present on both the source and destination but different.

The --combined flag will write a file (or stdout) which contains all file paths with a symbol and then a space and then the path to tell you what happened to it. These are reminiscent of diff files.

  • = path means path was found in source and destination and was identical
  • - path means path was missing on the source, so only in the destination
  • + path means path was missing on the destination, so only in the source
  • * path means path was present in source and destination but different.
  • ! path means there was an error reading or hashing the source or dest.

Read the full file on GitHub · 133 lines

Changes

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.

  1. 5d ago First seen · 133 lines · 10 tokens per session scan A 72f1b15ac7fb

Subscribe to this mod's changes

rclone_check is a command published in the GitHub repository olorehq/olore (103 stars, last pushed today), licensed MIT. It adds 10 tokens to every session and 1,444 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-09-03.