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.
git clone --depth 1 https://github.com/olorehq/oloreWrote 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.
[](https://agentmods.dev/commands/olorehq/olore/rclone_serve_docker)<a href="https://agentmods.dev/commands/olorehq/olore/rclone_serve_docker"><img src="https://agentmods.dev/badge/commands/olorehq/olore/rclone_serve_docker.svg" alt="Measured on agentmods" height="20"></a>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.1 | $0.00010 | $0.07527 |
| Opus 5 | $0.00005 | $0.03764 |
| Sonnet 5 | $0.00002 | $0.01505 |
| Haiku 4.5 | $0.00001 | $0.00753 |
Grade B, and why
rclone_serve_docker scanned grade B with 1 finding 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo rclone serve docker --base-dir /tmp/rclone-volumes --socket-addr localhost:8787 -vv This is a copy
84% identical to rclone_serve_dlna — 100 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 653 lines — stays where its author put it; the contents beside it link to each section on GitHub.
rclone serve docker
Serve any remote on docker's volume plugin API.
Synopsis
This command implements the Docker volume plugin API allowing docker to use rclone as a data storage mechanism for various cloud providers. rclone provides docker volume plugin based on it.
To create a docker plugin, one must create a Unix or TCP socket that Docker will look for when you use the plugin and then it listens for commands from docker daemon and runs the corresponding code when necessary. Docker plugins can run as a managed plugin under control of the docker daemon or as an independent native service. For testing, you can just run it directly from the command line, for example:
sudo rclone serve docker --base-dir /tmp/rclone-volumes --socket-addr localhost:8787 -vv
Running rclone serve docker will create the said socket, listening for
commands from Docker to create the necessary Volumes. Normally you need not
give the --socket-addr flag. The API will listen on the unix domain socket
at /run/docker/plugins/rclone.sock. In the example above rclone will create
a TCP socket and a small file /etc/docker/plugins/rclone.spec containing
the socket address. We use sudo because both paths are writeable only by
the root user.
If you later decide to change listening socket, the docker daemon must be
restarted to reconnect to /run/docker/plugins/rclone.sock
or parse new /etc/docker/plugins/rclone.spec. Until you restart, any
volume related docker commands will timeout trying to access the old socket.
Running directly is supported on Linux only, not on Windows or MacOS.
This is not a problem with managed plugin mode described in details
in the full documentation.
The command will create volume mounts under the path given by --base-dir
(by default /var/lib/docker-volumes/rclone available only to root)
and maintain the JSON formatted file docker-plugin.state in the rclone cache
directory with book-keeping records of created and mounted volumes.
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.
- 5d ago First seen · 653 lines · 10 tokens per session scan B c5413977a944
rclone_serve_docker is a command published in the GitHub repository olorehq/olore (103 stars, last pushed yesterday), licensed MIT. It adds 10 tokens to every session and 7,527 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). It is 84% identical to rclone_serve_dlna, differing in 100 lines, and is treated as a copy.
Other commands, from other repositories
create-docker-mcp-tunnel
Stand up an Anthropic MCP tunnel locally with Docker Compose so Claude can call a private MCP server (manual-credentials quickstart).
k8s-manifest
Generate production-ready Kubernetes manifests for the current application.
cisco-isovalent-platform-setup
Install the Isovalent platform on Kubernetes (Cilium CNI, Hubble observability, Tetragon eBPF runtime security) in either OSS or Enterprise edition. Renders Helm values and install/upgrade scripts; this is the platform install prerequisite for the Splunk Observability + Splunk Platform integration done by…
extract-infrastructure
Extract Azure infrastructure and generate Docker Compose stack for local development.
deploy
Deploy an app to multiple clusters with smart placement.
aci-run
Run a container in Azure Container Instances for quick one-off tasks or scheduled jobs.