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/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_selfupdate)<a href="https://agentmods.dev/commands/chaunsin/agent-skills/rclone_selfupdate"><img src="https://agentmods.dev/badge/commands/chaunsin/agent-skills/rclone_selfupdate/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.
<a href="https://agentmods.dev/commands/chaunsin/agent-skills/rclone_selfupdate"><img src="https://agentmods.dev/badge/commands/chaunsin/agent-skills/rclone_selfupdate.svg" alt="Reviewed on agentmods" width="80" 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.00006 | $0.00911 |
| Opus 5 | $0.00003 | $0.00456 |
| Sonnet 5 | $0.00001 | $0.00182 |
| Haiku 4.5 | $0.00001 | $0.00091 |
Grade A, and why
rclone_selfupdate 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.
This is a copy
94% identical to rclone_selfupdate — 2 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Official documentation: https://rclone.org/commands/rclone_selfupdate/
rclone selfupdate
Update the rclone binary.
Synopsis
This command downloads the latest release of rclone and replaces the currently running binary. The download is verified with a hashsum and cryptographically signed signature; see the release signing docs for details.
If used without flags (or with implied --stable flag), this command
will install the latest stable release. However, some issues may be fixed
(or features added) only in the latest beta release. In such cases you should
run the command with the --beta flag, i.e. rclone selfupdate --beta.
You can check in advance what version would be installed by adding the
--check flag, then repeat the command without it when you are satisfied.
Sometimes the rclone team may recommend you a concrete beta or stable
rclone release to troubleshoot your issue or add a bleeding edge feature.
The --version VER flag, if given, will update to the concrete version
instead of the latest one. If you omit micro version from VER (for
example 1.53), the latest matching micro version will be used.
Upon successful update rclone will print a message that contains a previous
version number. You will need it if you later decide to revert your update
for some reason. Then you'll have to note the previous version and run the
following command: rclone selfupdate [--beta] OLDVER.
If the old version contains only dots and digits (for example v1.54.0)
then it's a stable release so you won't need the --beta flag. Beta releases
have an additional information similar to v1.54.0-beta.5111.06f1c0c61.
(if you are a developer and use a locally built rclone, the version number
will end with -DEV, you will have to rebuild it as it obviously can't
be distributed).
If you previously installed rclone via a package manager, the package may
include local documentation or configure services. You may wish to update
with the flag --package deb or --package rpm (whichever is correct for
your OS) to update these too. This command with the default --package zip
will update only the rclone executable so the local manual may become
inaccurate after it.
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 · 92 lines · 6 tokens per session scan A 123b2468422e
rclone_selfupdate 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 911 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to rclone_selfupdate, differing in 2 lines, and is treated as a copy.
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.
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.
backlot
Open the Backlot living storyboard — the browser board that shows pipeline stages, script, scene plan, and generated assets live as a production runs.
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.
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.