What is rclone_cryptcheck?

An rclone command that checks whether files in an encrypted remote match the expected checksums. Rclone transfers files between local storage and remote services, while encryption protects their contents.

Use it to compare local files with an encrypted remote, or compare a regular remote with its encrypted counterpart. It can also perform a one-way check that ignores extra destination files.

It helps detect damaged or changed files without treating encrypted remote data like ordinary readable files. This gives you a way to verify encrypted backups or storage.

rclone_cryptcheck — Command by chaunsin

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.

agentmods

npx agentmods add commands/chaunsin/agent-skills/rclone_cryptcheck

Clone the repo

git clone --depth 1 https://github.com/chaunsin/agent-skills

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,450 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5	$0.00010	$0.01450
Opus 5	$0.00005	$0.00725
Sonnet 5	$0.00002	$0.00290
Haiku 4.5	$0.00001	$0.00145

Measured 2d ago against content hash caac7fb0485d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

skills/rclone-cli/references/commands/rclone_cryptcheck.md · 142 lines

How it starts

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

Official documentation: https://rclone.org/commands/rclone_cryptcheck/

rclone cryptcheck

Cryptcheck checks the integrity of an encrypted remote.

Synopsis

Checks a remote against an encrypted remote. This is the equivalent of running rclone check, but able to check the checksums of the encrypted remote.

For it to work the underlying remote of the cryptedremote must support some kind of checksum.

It works by reading the nonce from each file on the cryptedremote: and using that to encrypt each file on the remote:. It then checks the checksum of the underlying file on the cryptedremote: against the checksum of the file it has just encrypted.

Use it like this

rclone cryptcheck /path/to/files encryptedremote:path

You can use it like this also, but that will involve downloading all the files in remote:path.

rclone cryptcheck remote:path encryptedremote:path

After it has run it will log the status of the encryptedremote:.

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 · 142 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.

2d ago First seen · 142 lines · 10 tokens per session scan A caac7fb0485d

Subscribe to this mod's changes

rclone_cryptcheck is a command published in the GitHub repository chaunsin/agent-skills (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 10 tokens to every session and 1,450 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-31.

Security agent claude-code codex postgresql psql skills

rclone_cryptcheck

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

rclone cryptcheck

Synopsis

What this file has done since we first saw it

Other commands, from other repositories

install

search

agents-xml

use

remember

optimize