rclone_config_update

rclone_config_update is a command for coding agents from chaunsin/agent-skills. It costs 7 tokens per session (1,281 once invoked), scanned A, a copy of rclone_config_create, Apache-2.0.

A command for changing settings in an existing rclone storage connection, called a remote. It accepts option names and values, including settings such as authentication or an OAuth token.

In plain words
What is it for?
Use it in scripts or maintenance tasks to update remote options and credentials. Password values are automatically obscured before being saved.
Why use it?
It lets you adjust a connection without recreating it from scratch.

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_config_update
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_config_update

README.md
[![agentmods](https://agentmods.dev/badge/commands/chaunsin/agent-skills/rclone_config_update.svg)](https://agentmods.dev/commands/chaunsin/agent-skills/rclone_config_update)
Your own site
<a href="https://agentmods.dev/commands/chaunsin/agent-skills/rclone_config_update"><img src="https://agentmods.dev/badge/commands/chaunsin/agent-skills/rclone_config_update.svg" alt="Measured on agentmods" 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 1,281 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 92% copy Near-identical to another mod 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.00007 $0.01281
Opus 5 $0.00003 $0.00641
Sonnet 5 $0.00001 $0.00256
Haiku 4.5 $0.00001 $0.00128

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

Security

Grade A, and why

rclone_config_update 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

This is a copy

92% identical to rclone_config_create — 32 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.

skills/rclone-cli/references/commands/rclone_config_update.md · 151 lines

How it starts

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

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

rclone config update

Update options in an existing remote.

Synopsis

Update an existing remote's options. The options should be passed in pairs of key value or as key=value.

For example, to update the env_auth field of a remote of name myremote you would do:

rclone config update myremote env_auth true
rclone config update myremote env_auth=true

If the remote uses OAuth the token will be updated, if you don't require this add an extra parameter thus:

rclone config update myremote env_auth=true config_refresh_token=false

Note that if the config process would normally ask a question the default is taken (unless --non-interactive is used). Each time that happens rclone will print or DEBUG a message saying how to affect the value taken.

If any of the parameters passed is a password field, then rclone will automatically obscure them if they aren't already obscured before putting them in the config file.

NB If the password parameter is 22 characters or longer and consists only of base64 characters then rclone can get confused about whether the password is already obscured or not and put unobscured passwords into the config file. If you want to be 100% certain that the passwords get obscured then use the --obscure flag, or if you are 100% certain you are already passing obscured passwords then use --no-obscure. You can also set obscured passwords using the rclone config password command.

The flag --non-interactive is for use by applications that wish to configure rclone themselves, rather than using rclone's text based configuration questions. If this flag is set, and rclone needs to ask the user a question, a JSON blob will be returned with the question in it.

This will look something like (some irrelevant detail removed):

{
  "State": "*oauth-islocal,teamdrive,,",
  "Option": {
    "Name": "config_is_local",
    "Help": "Use web browser to automatically authenticate rclone with remote?\n * Say Y if the machine running rclone has a web browser you can use\n * Say N if running rclone on a (remote) machine without web browser access\nIf not sure try Y. If Y failed, try N.\n",
    "Default": true,
    "Examples": [
      {
        "Value": "true",
        "Help": "Yes"
      },
      {
        "Value": "false",
        "Help": "No"
      }
    ],
    "Required": false,
    "IsPassword": false,
    "Type": "bool",
    "Exclusive": true,
  },
  "Error": "",
}

Read the full file on GitHub · 151 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 · 151 lines · 7 tokens per session scan A 2b5a64b9fee7

Subscribe to this mod's changes

rclone_config_update is a command published in the GitHub repository chaunsin/agent-skills (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 7 tokens to every session and 1,281 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to rclone_config_create, differing in 32 lines, and is treated as a copy.

Related

Other commands, from other repositories

ink-art

Hand-drawn ink-on-white doodle animation — a character that draws itself then walks/dances/waves, or a deadpan contraption explainer. Vector, deterministic, rendered via HyperFrames to MP4.

calesthio/OpenMontage · 43 tokens

animated-drawing

Animate a SUPPLIED drawing/photo of a character with real motion capture (Meta AnimatedDrawings) → raster GIF/MP4 of that drawing moving. To CREATE a vector doodle from scratch, use /ink-art.

calesthio/OpenMontage · 0 tokens

backlot

Open the Backlot living storyboard — the browser board that shows pipeline stages, script, scene plan, and generated assets live as a production runs.

calesthio/OpenMontage · 29 tokens

README

Codex only scans /.codex/prompts/ (user home) for custom prompts — it does not read project-level .codex/prompts/. These files are versioned here as the source of truth; to use them in Codex, copy or symlink them into your home dir.

calesthio/OpenMontage · 0 tokens

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

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