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 skills/yongjip/mergetrain/deploynpx skills add yongjip/mergetrain --skill deploygit clone --depth 1 https://github.com/yongjip/mergetrainWrote 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/skills/yongjip/mergetrain/deploy)<a href="https://agentmods.dev/skills/yongjip/mergetrain/deploy"><img src="https://agentmods.dev/badge/skills/yongjip/mergetrain/deploy.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 | $0.00030 | $0.00207 |
| Opus 5 | $0.00015 | $0.00103 |
| Sonnet 5 | $0.00006 | $0.00041 |
| Haiku 4.5 | $0.00003 | $0.00021 |
Grade A, and why
deploy 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 today.
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.
What it actually says
Deploy one exact plan
- Call
mergetrain_statusand read its health, state, and next action. - Invoke
mergetrain_deploywithout selection or approval arguments. It may validate queued work, then presents the exact tasks, destination refs, and gate policy through the client's human confirmation dialog. Train IDs and plan hashes remain internal. - Do not substitute a shell deploy command or a model-supplied confirmation.
If the tool returns
confirmation_required, show its terminal command and stop. If it returnsdeploy_not_confirmed, report that nothing was pushed. - Report
result, deployed job IDs,deploy_sha,push_status, andverify_status.
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.
- today Changed · +14 tokens per session 9afb361f543a
- 4d ago First seen · 22 lines · 16 tokens per session scan A e8471c2189e8
deploy is a skill published in the GitHub repository yongjip/mergetrain (3 stars, last pushed today), licensed MIT. It adds 30 tokens to every session and 207 once invoked, about $0.0002 per session on Opus 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 skills, from other repositories
mulmoterminal-dirs
Colour-code and order the directories you actually work in, from wherever you are. Writes each project's /.mulmoterminal.json — name badge, project icon image, the seven chrome colours, xterm palette (theme / colors), terminal font size, orderPriority (where it sits in the grid and in the launcher's chips), and…
mulmoterminal-keys
Bind keyboard shortcuts and fix keyboard/clipboard behaviour in MulmoTerminal. Writes keymap, which Settings cannot set at all — its Keyboard shortcuts section is read-only, listing every action bound or not plus a send row. Explains copyOnSelect, questionPaneEnabled and terminalSubmit, which have their own Settings…
mulmoterminal-config
The way into configuring MulmoTerminal, and the way to find out how it is configured now. Use for a broad or unsure request — "configure MulmoTerminal", "set this up", "customize this", "what can I change?", first-run setup — and route to the skill that owns the area. Also answers "how is this set up right now?", "why…
mulmoterminal-model
Run MulmoTerminal sessions on something other than Anthropic's default, three ways — register an Anthropic-compatible backend (OpenRouter, Moonshot, a local Ollama bridge, a company gateway) as a providers entry in /.mulmoterminal/config.json, which has no Settings UI; pin a provider / model per project in its…
mulmoterminal-header
Put your own action buttons and info chips in a MulmoTerminal session header — either everywhere (buttons / chips in /.mulmoterminal/config.json, which has no Settings UI) or for one project ( /.mulmoterminal.json). Buttons run a shell command in a new cell, type text into the running agent (/compact), or open a URL…
mulmoterminal-notify
Decide which moments MulmoTerminal beeps or pushes for, and what each one plays — soundKinds, sounds and pushKinds in /.mulmoterminal/config.json, plus a per-project sound / sounds in /.mulmoterminal.json so one repo can have its own chime. Six moments exist (a turn finished, the agent is waiting on you, a Run command…