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 skills add ImL1s/agent-cli-skills --skill multi-cli-spawngit clone --depth 1 https://github.com/ImL1s/agent-cli-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/skills/iml1s/agent-cli-skills/multi-cli-spawn)<a href="https://agentmods.dev/skills/iml1s/agent-cli-skills/multi-cli-spawn"><img src="https://agentmods.dev/badge/skills/iml1s/agent-cli-skills/multi-cli-spawn/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/skills/iml1s/agent-cli-skills/multi-cli-spawn"><img src="https://agentmods.dev/badge/skills/iml1s/agent-cli-skills/multi-cli-spawn.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.00110 | $0.01075 |
| Opus 5.5 | $0.00044 | $0.00430 |
| Sonnet 5.5 | $0.00022 | $0.00215 |
| Haiku 4.5 | $0.00011 | $0.00108 |
Grade A, and why
multi-cli-spawn 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.
How it starts
The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Multi-CLI Spawn (cross-provider parallel seats)
When to use
- Need several providers to answer the same brief in parallel
- Multi-LLM council / second opinions / cross-vendor review
- You already have (or will install) the per-CLI
*-cli-agentwrappers
This is not a substitute for vendor-native multi-agent inside one CLI (-T / ultracode /
teamwork). Use those for fan-out within one provider; use this skill to fan-out across providers.
Why
Each vendor has native multi-agent inside one CLI (agy teamwork, Claude ultracode, Codex subagents, Grok spawn_subagent, …). This skill is the cross-CLI layer: one brief → N providers → N answer files.
Usage
./spawn.sh --outdir /tmp/council-$$ \
-f /tmp/brief.md \
--seat agy:readonly \
--seat claude:ultracode \
--seat codex:team \
--seat grok \
--seat kimi:readonly \
--seat qwen:readonly \
-C /path/to/repo \
-t 1200s
Seat forms: name, name:readonly, name:ultracode|team, name:readonly,team, name@label
(unique output key when duplicating a CLI).
Seat modifiers (comma-separated after :): readonly/r, team/ultracode/T.
Outputs
| File | Meaning |
|---|---|
<key>.log |
Live CLI stdout/stderr |
<key>.md |
Final answer, or BLOCKED:… stub (written when the seat finishes) |
<key>.pid |
Seat process-group id (kill target) |
<key>.rc |
Seat exit code |
<key>.status |
RUNNING → DONE rc=0 | BLOCKED rc=N (atomic) |
spawn.pid / spawn.status |
Parent: RUNNING → DONE, or SPAWNED if --no-wait |
brief.md |
Copied/normalized brief inside outdir |
Waiting contract
- Default: do not poll. Run
spawn.shin the foreground (wait mode). Its exit code andCLI_AGENT_RESULT: PASS|BLOCKED <seat>lines are the completion signal. --no-wait/ external watcher: wait until every seat.statusis terminal (DONE/BLOCKED), e.g.:
Do not treat missingwhile grep -qlE '^RUNNING' "$OUTDIR"/*.status 2>/dev/null; do sleep 15; done*.mdor a dead*.pidalone as "no answer" —.mdappears only when the seat finishes; pidfiles can look dead if the parent spawn was killed while seats continue.- Kill only via numeric PIDs in seat
*.pidfiles (process groups). Skipspawn.pidwhen iterating kill targets unless you intend to stop the parent. Neverpkill -flong patterns.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 90 lines · 110 tokens per session scan A 04a736dd4064
multi-cli-spawn is a skill published in the GitHub repository ImL1s/agent-cli-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 110 tokens to every session and 1,075 once invoked, about $0.0004 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 skills, from other repositories
agent-browser
Use the host-side agent-browser CLI for local browser smoke tests, screenshots, snapshots, and simple UI validation against forwarded localhost URLs.
agent-desktop
Use the built-in Computer sub-agent with agent-desktop for macOS desktop automation. Apply when a task needs application launching, accessibility snapshots, stable element refs, window focusing, semantic clicks/typing, or visual confirmation outside the browser sandbox.
find-skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
wttr-weather
Weather via wttr.in GET (no key). Use for weather/forecast; prefer os.http.request.
jk
Manage Jenkins controllers with jk, including jobs, runs, logs, artifacts, credentials, nodes, queues, and plugins.
financial-analysis
Financial figures done carefully: periods and fiscal calendars, units and currencies, reconciliation, magnitude sanity checks, sourced assumptions. Use for statements, budgets, pricing, and diligence numbers.