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.
npx agentmods add commands/chaunsin/agent-skills/rclone_config_encryptiongit clone --depth 1 https://github.com/chaunsin/agent-skillsWrote 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/chaunsin/agent-skills/rclone_config_encryption)<a href="https://agentmods.dev/commands/chaunsin/agent-skills/rclone_config_encryption"><img src="https://agentmods.dev/badge/commands/chaunsin/agent-skills/rclone_config_encryption.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 | $0.00011 | $0.00291 |
| Opus 5 | $0.00005 | $0.00146 |
| Sonnet 5 | $0.00002 | $0.00058 |
| Haiku 4.5 | $0.00001 | $0.00029 |
Grade A, and why
rclone_config_encryption 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 3d 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.
What it actually says
Official documentation: https://rclone.org/commands/rclone_config_encryption/
rclone config encryption
set, remove and check the encryption for the config file
Synopsis
This command sets, clears and checks the encryption for the config file using the subcommands below.
Options
-h, --help help for encryption
See the global flags page for global options not listed here.
See Also
- rclone config - Enter an interactive configuration session.
- rclone config encryption check - Check that the config file is encrypted
- rclone config encryption remove - Remove the config file encryption password
- rclone config encryption set - Set or change the config file encryption password
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.
- 3d ago First seen · 37 lines · 11 tokens per session scan A 317d67f00b07
rclone_config_encryption is a command published in the GitHub repository chaunsin/agent-skills (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 11 tokens to every session and 291 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.
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.
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.
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.
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.
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…
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.