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_gitannex)<a href="https://agentmods.dev/commands/chaunsin/agent-skills/rclone_gitannex"><img src="https://agentmods.dev/badge/commands/chaunsin/agent-skills/rclone_gitannex/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_gitannex"><img src="https://agentmods.dev/badge/commands/chaunsin/agent-skills/rclone_gitannex.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.00011 | $0.00879 |
| Opus 5.5 | $0.00004 | $0.00352 |
| Sonnet 5.5 | $0.00002 | $0.00176 |
| Haiku 4.5 | $0.00001 | $0.00088 |
Grade A, and why
rclone_gitannex 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 2mo 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
89% identical to rclone_gitannex — 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_gitannex/
rclone gitannex
Speaks with git-annex over stdin/stdout.
Synopsis
Rclone's gitannex subcommand enables git-annex to store and retrieve content
from an rclone remote. It is meant to be run by git-annex, not directly by
users.
Installation on Linux
-
Skip this step if your version of git-annex is 10.20240430 or newer. Otherwise, you must create a symlink somewhere on your PATH with a particular name. This symlink helps git-annex tell rclone it wants to run the "gitannex" subcommand.
Create the helper symlink in "$HOME/bin":
ln -s "$(realpath rclone)" "$HOME/bin/git-annex-remote-rclone-builtin" Verify the new symlink is on your PATH: ```console which git-annex-remote-rclone-builtin -
Add a new remote to your git-annex repo. This new remote will connect git-annex with the
rclone gitannexsubcommand.Start by asking git-annex to describe the remote's available configuration parameters.
If you skipped step 1:
git annex initremote MyRemote type=rclone --whatelseIf you created a symlink in step 1:
git annex initremote MyRemote type=external externaltype=rclone-builtin --whatelseNOTE: If you're porting an existing git-annex-remote-rclone remote to use
rclone gitannex, you can probably reuse the configuration parameters verbatim without renaming them. Check parameter synonyms with--whatelseas shown above.The following example creates a new git-annex remote named "MyRemote" that will use the rclone remote named "SomeRcloneRemote". That rclone remote must be one configured in your rclone.conf file, which can be located with
rclone config file.git annex initremote MyRemote \ type=external \ externaltype=rclone-builtin \ encryption=none \ rcloneremotename=SomeRcloneRemote \ rcloneprefix=git-annex-content \ rclonelayout=nodir -
Before you trust this command with your precious data, be sure to test the remote. This command is very new and has not been tested on many rclone backends. Caveat emptor!
git annex testremote MyRemote
Happy annexing!
rclone gitannex [flags]
Options
-h, --help help for gitannex
See the global flags page for global options not listed here.
See Also
- rclone - Show help for rclone commands, flags and backends.
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.
- 2mo ago First seen · 114 lines · 11 tokens per session scan A d4d85d99aeaf
rclone_gitannex is a command published in the GitHub repository chaunsin/agent-skills (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 11 tokens to every session and 879 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to rclone_gitannex, differing in 2 lines, and is treated as a copy.
Other commands, from other repositories
release
Verify, write the CHANGELOG, cut a version — then hand the release sequence back.
release
Command "release" from voodootikigod/skills-check, covering arguments and steps.
project
Manage projects: register repos, inspect, configure per-project settings, and remove.
commit-push-pr
Commit, push, and open a PR.
devkit.github.review-pr
Provides comprehensive GitHub pull request review with code quality, security, and best practices analysis. Use when reviewing a PR before merging.
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.