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_serve_s3)<a href="https://agentmods.dev/commands/chaunsin/agent-skills/rclone_serve_s3"><img src="https://agentmods.dev/badge/commands/chaunsin/agent-skills/rclone_serve_s3/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_serve_s3"><img src="https://agentmods.dev/badge/commands/chaunsin/agent-skills/rclone_serve_s3.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.00007 | $0.09128 |
| Opus 5 | $0.00003 | $0.04564 |
| Sonnet 5 | $0.00001 | $0.01826 |
| Haiku 4.5 | $0.00001 | $0.00913 |
Grade A, and why
rclone_serve_s3 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 6d 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
98% identical to rclone_serve_s3 — 9 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 — 868 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Official documentation: https://rclone.org/commands/rclone_serve_s3/
rclone serve s3
Serve remote:path over s3.
Synopsis
serve s3 implements a basic s3 server that serves a remote via s3.
This can be viewed with an s3 client, or you can make an s3 type
remote to read and write to it with rclone.
serve s3 is considered Experimental so use with care.
S3 server supports Signature Version 4 authentication. Just use
--auth-key accessKey,secretKey and set the Authorization
header correctly in the request. (See the AWS
docs).
--auth-key can be repeated for multiple auth pairs. If
--auth-key is not provided then serve s3 will allow anonymous
access.
Like all rclone flags --auth-key can be set via environment
variables, in this case RCLONE_AUTH_KEY. Since this flag can be
repeated, the input to RCLONE_AUTH_KEY is CSV encoded. Because the
accessKey,secretKey has a comma in, this means it needs to be in
quotes.
export RCLONE_AUTH_KEY='"user,pass"'
rclone serve s3 ...
Or to supply multiple identities:
export RCLONE_AUTH_KEY='"user1,pass1","user2,pass2"'
rclone serve s3 ...
Setting this variable without quotes will produce an error.
Please note that some clients may require HTTPS endpoints. See the SSL docs for more information.
This command uses the VFS directory cache.
All the functionality will work with --vfs-cache-mode off. Using
--vfs-cache-mode full (or writes) can be used to cache objects
locally to improve performance.
Use --force-path-style=false if you want to use the bucket name as a
part of the hostname (such as mybucket.local)
Use --etag-hash if you want to change the hash uses for the ETag.
Note that using anything other than MD5 (the default) is likely to
cause problems for S3 clients which rely on the Etag being the MD5.
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.
- 6d ago First seen · 868 lines · 7 tokens per session scan A 521afcbc9776
rclone_serve_s3 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 9,128 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to rclone_serve_s3, differing in 9 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.
deploy-setup
Wire CI + secrets for a fresh storefront. Run once after /init-store before the first push to main.
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.