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_completion)<a href="https://agentmods.dev/commands/chaunsin/agent-skills/rclone_completion"><img src="https://agentmods.dev/badge/commands/chaunsin/agent-skills/rclone_completion/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_completion"><img src="https://agentmods.dev/badge/commands/chaunsin/agent-skills/rclone_completion.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.00008 | $0.00326 |
| Opus 5.5 | $0.00003 | $0.00130 |
| Sonnet 5.5 | $0.00002 | $0.00065 |
| Haiku 4.5 | $0.00001 | $0.00033 |
Grade A, and why
rclone_completion 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 1mo 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_completion — 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_completion/
rclone completion
Output completion script for a given shell.
Synopsis
Generates a shell completion script for rclone.
Run with --help to list the supported shells.
Options
-h, --help help for completion
See the global flags page for global options not listed here.
See Also
- rclone - Show help for rclone commands, flags and backends.
- rclone completion bash - Output bash completion script for rclone.
- rclone completion fish - Output fish completion script for rclone.
- rclone completion powershell - Output powershell completion script for rclone.
- rclone completion zsh - Output zsh completion script for rclone.
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.
- 1mo ago First seen · 41 lines · 8 tokens per session scan A c514f3074e65
rclone_completion is a command published in the GitHub repository chaunsin/agent-skills (2 stars, last pushed 24d ago), licensed Apache-2.0. It adds 8 tokens to every session and 326 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to rclone_completion, differing in 2 lines, and is treated as a copy.
Other commands, from other repositories
root-cause
Use when any test fails, bug appears, or behaviour surprises you, before proposing a fix - find the cause and prove it, by reading real evidence, tracing bad values back to their origin, comparing against a working case, and testing one hypothesis at a time.
init
Generate FILETREE.md from scratch. Confirms overwrite if it already exists. --self-only keeps every artifact out of git.
uninstall
Uninstall filetree from this repo — un-wires CLAUDE.md/AGENTS.md, removes generated artifacts (confirmed per item), tears down self-only mode if enabled.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.