Scion is a multi-agent orchestration platform that runs several isolated agents concurrently in containers, optionally giving each one its own workspace and credentials. It is used to coordinate coding and other research or operations tasks across local machines, remote virtual machines, and Kubernetes clusters. Catalogue add-ons provide workflows and controls for operating Scion.
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/googlecloudplatform/scion/scion-agent-managenpx skills add GoogleCloudPlatform/scion --skill scion-agent-managegit clone --depth 1 https://github.com/GoogleCloudPlatform/scionWrote 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/googlecloudplatform/scion/scion-agent-manage)<a href="https://agentmods.dev/skills/googlecloudplatform/scion/scion-agent-manage"><img src="https://agentmods.dev/badge/skills/googlecloudplatform/scion/scion-agent-manage.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.00031 | $0.01090 |
| Opus 5 | $0.00015 | $0.00545 |
| Sonnet 5 | $0.00006 | $0.00218 |
| Haiku 4.5 | $0.00003 | $0.00109 |
Grade A, and why
scion-agent-manage 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 5d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scion Agent Management Skill
Scion is a container-based orchestration tool for managing concurrent LLM-based code agents. It enables parallel execution of specialized sub-agents with isolated identities, credentials, and workspaces.
Core Concepts
Projects
A project is the grouping construct for agents in scion.
Agents
An agent is an isolated LLM instance running in a container with a mounted workspace, credentials, and configuration.
Templates
Templates are blueprints for creating agents.
Harnesses
A harness is the LLM interface (Gemini CLI, Claude Code, etc.) that the agent uses.
Command Reference
The best and most current reference for the CLI commands is available from scion --help. Some best practices are in the scion-cli-operations skill.
Tips for Agents
-
Check existing agents first: Before starting a new agent, use
scion listto see what's already running. -
Use descriptive names: Agent names should reflect their purpose (e.g.,
refactor-auth,test-api,audit-security). -
Choose appropriate templates: Use
--type researcherfor a researcher. -
Monitor with logs: Use
scion logs <agent>to check progress without interrupting. -
Interrupt carefully: The
--interruptflag on messages stops current work - use only when necessary. -
Preserve branches: Use
--preserve-branchto keep the branch after deletion for later review. The flag does not push — confirm the branch is on the remote first. -
Agent state: Do not attempt to resume an agent unless you were the one who stopped it. An 'idle' agent may still be working.
Creating Agents
To translate a natural-language request into a scion start command, map intent to flags:
| Intent | Flag | Example |
|---|---|---|
| Agent role | -t / --type |
-t developer, -t researcher, -t code-reviewer |
| LLM interface | --harness |
--harness claude, --harness gemini-cli |
| Model override | --model |
--model claude-sonnet-4-20250514 |
What ships with it
2 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.
- 5d ago First seen · 111 lines · 31 tokens per session scan A 0c9b3d103600
scion-agent-manage is a skill published in the GitHub repository GoogleCloudPlatform/scion (1,687 stars, last pushed yesterday), licensed Apache-2.0. It adds 31 tokens to every session and 1,090 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…