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/greenpolo/cc-multi-cli-plugin/multi-cli-anythingnpx skills add greenpolo/cc-multi-cli-plugin --skill multi-cli-anythinggit clone --depth 1 https://github.com/greenpolo/cc-multi-cli-pluginWhat 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.00116 | $0.07180 |
| Opus 5 | $0.00058 | $0.03590 |
| Sonnet 5 | $0.00023 | $0.01436 |
| Haiku 4.5 | $0.00012 | $0.00718 |
Grade B, and why
multi-cli-anything scanned grade B with 1 finding 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 yesterday.
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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- **MCP wiring.** If the user needs MCP tools, confirm they fire. Many CLIs read MCP servers from their **own config file** (Cursor: `~/.cursor/mcp.json`; Codex: `~/.codex/config.toml`; Antigravity/agy: `~/.gemini/settin How it starts
The opening of the file, as written. The whole thing — 353 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add a new CLI to cc-multi-cli-plugin
cc-multi-cli-plugin is a multi-plugin marketplace with four built-in CLIs: Codex, Cursor, Antigravity, and OpenCode. Adding a new CLI beyond these means two things:
- A new adapter in the
multihub —plugins/multi/scripts/lib/adapters/<cli>.mjs— that conforms to the adapter contract and is registered inlib/adapters/registry.mjs, plus a dispatch branch inlib/commands/task.mjs. - A new thin plugin —
plugins/<cli>/with command files + aplugin.json, registered in the rootmarketplace.json— that forwards/<cli>:<role>into the hub viamulti:<cli>-<role>subagents.
The adapter interface is transport-agnostic. The companion consumes only the five-method adapter object defined in plugins/multi/scripts/lib/adapters/CONTRACT.md (name, isAvailable, isAuthenticated, invoke, cancel, plus optional getSession). How the adapter talks to the CLI — headless print mode, spawn-and-read-files, app-server HTTP, or (legacy) ACP — is your choice, driven by what the CLI actually exposes. Read CONTRACT.md first; it's the source of truth for the result shape.
There is no buildPrompt() function and no slash-command-prefix layer (an older design that's gone). A role's read/write behavior is expressed as CLI flags/sandbox inside the adapter; a role's prompt framing lives in its subagent .md. Don't reintroduce a buildPrompt.
Step 0 — Research the CLI first
Before writing any code, pull everything you need so you don't guess or ask the user later:
- Install status and binary name — is the user's machine set up? What's the exact command (
agent?qwen?aider?opencode?). - A drivable headless transport — see Prerequisites below. This is the make-or-break question.
- Exact model identifiers the CLI accepts (or
autoif offered). A wrong model string causes a 400/exit-1 at runtime. - Modes / permission flags — read-only vs write, an
ask/planmode, a--force/--yoloauto-approve flag, a sandbox setting. These are what you'll map roles onto inside the adapter. - Runtime flags — output format (
--output-format json?), resume/session, background — what does--helpactually list? - Authentication mechanism — env var, OAuth keyring, device code, API key header.
- Known quirks (Windows shell requirements, PATH issues, empty-stdout-when-piped bugs, version-specific behavior).
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.
- yesterday First seen · 353 lines · 116 tokens per session scan B 7bd8dd447ab5
multi-cli-anything is a skill published in the GitHub repository greenpolo/cc-multi-cli-plugin (89 stars, last pushed 16d ago), licensed Apache-2.0. It adds 116 tokens to every session and 7,180 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
copilot-pr-review-loop
Drive a GitHub pull request through repeated rounds of Copilot code review until convergence. Use when the user asks to "request Copilot review", "run a Copilot review loop", iterate on Copilot feedback, or wants automated triage-and-respond on Copilot PR comments. Covers re-request mechanics, open-thread filtering…
upstream-sync
Periodically sync new commits from microsoft/terminal into this manually-forked intelligent-terminal repo by cherry-picking commit-by-commit onto a dated sync branch, auto-skipping revert pairs and empty commits, auto-resolving known take-upstream files, and stopping cleanly on genuine conflicts. The agent (you…
release-notes
Generate user-facing release notes for Intelligent Terminal. Use when asked to write release notes, changelog, what-is-new summary, or prepare a release. Compares git commits between releases, looks up PR-linked issues and community contributors, then outputs formatted notes with "Verbed + Impact + Scenario" style…
add-acp-agent-support
Add first-class support for an ACP-compatible agent CLI to Intelligent Terminal. Use when integrating a new built-in AI agent, ACP server command, authentication flow, model selection, interactive delegation, session hooks, onboarding, Settings, branding, GPO policy, documentation, tests, build, deployment, or live…
pr-integration-test
Design, implement, and validate Intelligent Terminal integration tests for a target pull request or regression. Use when asked to add PR integration tests, convert a bug fix into E2E coverage, prove existing behavior still works, map tests to the release checklist, or verify E2E reports mark checklist cases complete.
opentag
Use when installing, pairing, operating, or troubleshooting OpenTag through the published CLI, self-hosted Control Plane, governed completion, supported collaboration platforms, or built-in coding agents.