Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add arcobaleno64/agy-plugin-cc/plugin install geminiWrote 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/arcobaleno64/agy-plugin-cc/transfer)<a href="https://agentmods.dev/commands/arcobaleno64/agy-plugin-cc/transfer"><img src="https://agentmods.dev/badge/commands/arcobaleno64/agy-plugin-cc/transfer/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/arcobaleno64/agy-plugin-cc/transfer"><img src="https://agentmods.dev/badge/commands/arcobaleno64/agy-plugin-cc/transfer.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.00022 | $0.00708 |
| Opus 5.5 | $0.00009 | $0.00283 |
| Sonnet 5.5 | $0.00004 | $0.00142 |
| Haiku 4.5 | $0.00002 | $0.00071 |
Grade A, and why
transfer 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.
How it starts
The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The user's raw arguments, as text and nothing else:
$ARGUMENTS
Those arguments must never reach a shell
This command deliberately does not pre-execute anything. $ARGUMENTS is
substituted into this file as text, so a shell receiving it would evaluate
whatever it contains — $(…), backticks, ;, |. Measured on the sibling job
commands: $(echo INJECTED) was executed before Node ever started.
Instructions here are free text, so there is no safe way to quote them into a command line. Write them to a file instead:
- Read the argument text above and separate it into two parts: the recognised flags, and everything else, which is the instruction text.
- Use the Write tool — not a shell — to put the instruction text in a file. A path under the system temp directory is fine; do not build the path from the user's text.
- Run the transfer, assembling the command from fixed pieces only:
node "${CLAUDE_PLUGIN_ROOT}/scripts/transfer.mjs" --instructions-file <the path you just wrote> [--engine <value>] [--model <value>] [--effort <value>]
The only flags you may pass are --engine, --model and --effort, and their
values must be ones you checked against the sets below — chosen from the list,
never copied from the argument text:
--engine:auto,gemini,agy--effort:low,medium,high,xhigh--model: an alias (flash,pro,lite, …) or a model id, which must match^[A-Za-z0-9][A-Za-z0-9._-]*$. If it does not, stop and say so.
If there are no instructions, omit --instructions-file entirely.
Presenting the result
Present the command output to the user exactly as returned. Preserve:
- The snapshot path under
.omc/transfers/ - Every generated launch command verbatim, including its quoting — the prompt is already shell-escaped for the target shell, and rewriting or reflowing it breaks the handoff
- Both the Bash/Zsh and PowerShell variants whenever both are printed
Do not run the generated commands. They are for the user to paste into an interactive terminal.
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 · 60 lines · 22 tokens per session scan A a791782ed0f2
transfer is a command published in the GitHub repository arcobaleno64/agy-plugin-cc (14 stars, last pushed 3d ago), licensed MIT. It adds 22 tokens to every session and 708 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
review
Get an independent cross-model review of the current diff from Antigravity (Gemini), then reconcile as the final judge.
merge-check
A pre-merge checklist command for a GitHub pull request. A pull request is a proposed code change, and the command checks whether it meets the project’s documented requirements before merging.
release-kick
A release command for the River Review project that checks release instructions and pull-request state, updates an out-of-date branch, and verifies the release after merging.
plan-merge-order
A command that plans the order for merging several pull requests (PRs), which are proposed code changes reviewed before entering a shared branch. It checks their status and file changes, then studies dependencies and overlap to reduce rebasing work.
verify-agent-report
A command for checking whether an agent’s reported branch, pull request, commit, or files actually exist. A pull request is a proposed code change submitted for review.
preflight
A pre-work check for finding whether a coding task or pull request is already finished, obsolete, or being handled elsewhere. A pull request is a proposed change to a code repository.