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_touchgit 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_touch)<a href="https://agentmods.dev/commands/chaunsin/agent-skills/rclone_config_touch"><img src="https://agentmods.dev/badge/commands/chaunsin/agent-skills/rclone_config_touch.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.1 | $0.00005 | $0.00191 |
| Opus 5 | $0.00003 | $0.00096 |
| Sonnet 5 | $0.00001 | $0.00038 |
| Haiku 4.5 | $0.00001 | $0.00019 |
Grade A, and why
rclone_config_touch 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
88% identical to rclone_config_touch — 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.
What it actually says
Official documentation: https://rclone.org/commands/rclone_config_touch/
rclone config touch
Ensure configuration file exists.
rclone config touch [flags]
Options
-h, --help help for touch
See the global flags page for global options not listed here.
See Also
- rclone config - Enter an interactive configuration session.
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 · 34 lines · 5 tokens per session scan A 943095834019
rclone_config_touch is a command published in the GitHub repository chaunsin/agent-skills (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 5 tokens to every session and 191 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to rclone_config_touch, 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.
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.