rclone_backend

rclone_backend is a command for coding agents from chaunsin/agent-skills. It costs 6 tokens per session (518 once invoked), scanned A, original, Apache-2.0.

An rclone command for running operations defined by a specific storage provider. A provider, also called a backend, is the part that connects rclone to a service such as cloud storage.

In plain words
What is it for?
Use it to run backend operations, inspect provider features, or pass provider-specific options and arguments.
Why use it?
It exposes provider-specific functions that ordinary rclone commands may not cover. Help and feature commands show what the selected provider supports.

Command

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_backend
Clone the repo
git clone --depth 1 https://github.com/chaunsin/agent-skills

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_backend

README.md
[![agentmods](https://agentmods.dev/badge/commands/chaunsin/agent-skills/rclone_backend.svg)](https://agentmods.dev/commands/chaunsin/agent-skills/rclone_backend)
Your own site
<a href="https://agentmods.dev/commands/chaunsin/agent-skills/rclone_backend"><img src="https://agentmods.dev/badge/commands/chaunsin/agent-skills/rclone_backend.svg" alt="Measured on agentmods" height="20"></a>
Per session 6 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 518 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.

ModelPer sessionOnce invoked
Fable 5 $0.00006 $0.00518
Opus 5 $0.00003 $0.00259
Sonnet 5 $0.00001 $0.00104
Haiku 4.5 $0.00001 $0.00052

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

Security

Grade A, and why

rclone_backend 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 4d 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_backend.md · 83 lines

What it actually says

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

rclone backend

Run a backend-specific command.

Synopsis

This runs a backend-specific command. The commands themselves (except for "help" and "features") are defined by the backends and you should see the backend docs for definitions.

You can discover what commands a backend implements by using

rclone backend help remote:
rclone backend help <backendname>

You can also discover information about the backend using (see operations/fsinfo in the remote control docs for more info).

rclone backend features remote:

Pass options to the backend command with -o. This should be key=value or key, e.g.:

rclone backend stats remote:path stats -o format=json -o long

Pass arguments to the backend by placing them on the end of the line

rclone backend cleanup remote:path file1 file2 file3

Note to run these commands on a running backend then see backend/command in the rc docs.

rclone backend <command> remote:path [opts] <args> [flags]

Options

  -h, --help                 help for backend
      --json                 Always output in JSON format
  -o, --option stringArray   Option in the form name=value or name

Options shared with other commands are described next. See the global flags page for global options not listed here.

Important Options

Important flags useful for most commands

  -n, --dry-run         Do a trial run with no permanent changes
  -i, --interactive     Enable interactive mode
  -v, --verbose count   Print lots more stuff (repeat for more)

See Also

  • rclone - Show help for rclone commands, flags and backends.
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. 4d ago First seen · 83 lines · 6 tokens per session scan A 99be5d18b577

Subscribe to this mod's changes

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

Related

Other commands, from other repositories

create-spec

Generate comprehensive feature specifications using a contract-first approach that ensures complete alignment between developer and AI before creating any supporting files. This command eliminates presumptuous file creation by establishing a clear "contract" through structured clarification rounds.

devobsessed/code-captain · 0 tokens

create-adr

Create comprehensive Architecture Decision Records (ADRs) that systematically document architectural decisions with clear rationale, alternatives considered, and consequences through a structured analysis and review process.

devobsessed/code-captain · 0 tokens

execute-task

Execute a specific task and its sub-tasks systematically following a Test-Driven Development (TDD) workflow. This command reads task specifications from .code-captain/specs/ directories and implements features with comprehensive testing, following established code standards and best practices.

devobsessed/code-captain · 0 tokens

initialize

Set up technical foundation and development infrastructure by detecting if this is a greenfield (new) or brownfield (existing) project and executing the appropriate technical setup workflow.

devobsessed/code-captain · 0 tokens

plan-product

Generate comprehensive product planning documentation using a contract-first approach that establishes clear product vision, mission, and roadmap before creating any supporting files. This command eliminates assumptions by gathering complete product context through structured discovery, then creates a complete product…

devobsessed/code-captain · 0 tokens

status

A command that provides developers with a comprehensive status report when starting work or switching context. Analyzes current git state, active work, and project health to orient developers and suggest next actions.

devobsessed/code-captain · 0 tokens