rclone_serve_s3

rclone_serve_s3 is a command for Claude Code from olorehq/olore. It costs 7 tokens per session (9,176 once invoked), scanned A, original, MIT.

An experimental S3-compatible server that exposes an rclone remote to S3 clients. S3 is a common API for storing and retrieving objects.

In plain words
What is it for?
Connecting S3 clients or rclone S3 remotes to an rclone-backed storage path.
Why use it?
It lets S3-based software use cloud providers supported by rclone. Access can be anonymous or protected with S3 Signature Version 4 credentials.

Command for Claude Code

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

Good fit Connecting S3 clients or rclone S3 remotes to an rclone-backed storage path.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/olorehq/olore/rclone_serve_s3
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_serve_s3

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/olorehq/olore/rclone_serve_s3"><img src="https://agentmods.dev/badge/commands/olorehq/olore/rclone_serve_s3.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 7 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 9,176 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.00007 $0.09176
Opus 5 $0.00003 $0.04588
Sonnet 5 $0.00001 $0.01835
Haiku 4.5 $0.00001 $0.00918

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

Security

Grade A, and why

rclone_serve_s3 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 6d 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_serve_s3.md · 873 lines

How it starts

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

rclone serve s3

Serve remote:path over s3.

Synopsis

serve s3 implements a basic s3 server that serves a remote via s3. This can be viewed with an s3 client, or you can make an s3 type remote to read and write to it with rclone.

serve s3 is considered Experimental so use with care.

S3 server supports Signature Version 4 authentication. Just use --auth-key accessKey,secretKey and set the Authorization header correctly in the request. (See the AWS docs).

--auth-key can be repeated for multiple auth pairs. If --auth-key is not provided then serve s3 will allow anonymous access.

Like all rclone flags --auth-key can be set via environment variables, in this case RCLONE_AUTH_KEY. Since this flag can be repeated, the input to RCLONE_AUTH_KEY is CSV encoded. Because the accessKey,secretKey has a comma in, this means it needs to be in quotes.

export RCLONE_AUTH_KEY='"user,pass"'
rclone serve s3 ...

Or to supply multiple identities:

export RCLONE_AUTH_KEY='"user1,pass1","user2,pass2"'
rclone serve s3 ...

Setting this variable without quotes will produce an error.

Please note that some clients may require HTTPS endpoints. See the SSL docs for more information.

This command uses the VFS directory cache. All the functionality will work with --vfs-cache-mode off. Using --vfs-cache-mode full (or writes) can be used to cache objects locally to improve performance.

Use --force-path-style=false if you want to use the bucket name as a part of the hostname (such as mybucket.local)

Use --etag-hash if you want to change the hash uses for the ETag. Note that using anything other than MD5 (the default) is likely to cause problems for S3 clients which rely on the Etag being the MD5.

Quickstart

For a simple set up, to serve remote:path over s3, run the server like this:

rclone serve s3 --auth-key ACCESS_KEY_ID,SECRET_ACCESS_KEY remote:path

Read the full file on GitHub · 873 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. 6d ago First seen · 873 lines · 7 tokens per session scan A 6dbd64d92182

Subscribe to this mod's changes

rclone_serve_s3 is a command published in the GitHub repository olorehq/olore (103 stars, last pushed today), licensed MIT. It adds 7 tokens to every session and 9,176 once invoked, about $0.0000 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.