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 skills add GoogleCloudPlatform/scion --skill team-creationgit 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/team-creation)<a href="https://agentmods.dev/skills/googlecloudplatform/scion/team-creation"><img src="https://agentmods.dev/badge/skills/googlecloudplatform/scion/team-creation/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/googlecloudplatform/scion/team-creation"><img src="https://agentmods.dev/badge/skills/googlecloudplatform/scion/team-creation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 134 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00093 | $0.02987 |
| Opus 5.5 | $0.00037 | $0.01195 |
| Sonnet 5.5 | $0.00019 | $0.00597 |
| Haiku 4.5 | $0.00009 | $0.00299 |
Grade A, and why
team-creation 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 — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scion Team Creation & Extension Skill
You create and extend scion agent templates — the blueprints that define specialized agent roles. Given a description of a team (roles, responsibilities, workflow), you produce template directories that can be used to start agents with scion start <name> --type <template>.
When extending an existing team, review the current templates to understand the established patterns, naming, and workflow before making changes.
Template Directory Structure
Each template lives in .scion/templates/<template-name>/ and contains:
.scion/templates/<template-name>/
├── scion-agent.yaml # REQUIRED: template metadata and config
├── agents.md # REQUIRED: agent behavioral instructions
├── system-prompt.md # REQUIRED: role persona and expertise framing
└── skills/ # OPTIONAL: harness skills (agentskills.io standard)
└── <skill-name>/
└── SKILL.md
Custom templates automatically inherit from the built-in default template, which provides shell configs, git setup, and base scion infrastructure. You do NOT need to create a home/ directory or duplicate any infrastructure files.
Template Naming
- Directory names use kebab-case:
panel-judge,code-reviewer,team-lead - Names should be descriptive of the role, not the project
Required File Formats
scion-agent.yaml
Every template MUST have this file. Minimal valid config:
schema_version: "1"
description: "Short description of this agent role"
agent_instructions: agents.md
system_prompt: system-prompt.md
Optional fields you may include when the role requires them:
max_turns: 50 # Maximum conversation turns
max_duration: "30m" # Maximum wall-clock time (e.g. "1h", "30m")
env:
ROLE: "reviewer"
services:
- name: chromium
command: ["chromium", "--headless", "--no-sandbox", "--remote-debugging-port=9222"]
restart: always
ready_check:
type: tcp
target: "localhost:9222"
timeout: "10s"
skills:
- uri: "skill://scion/global/idea-refine@latest"
- uri: "skill://scion/core/scion@^1.0"
optional: true
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 · 287 lines · 93 tokens per session scan A 464dd86d855c
team-creation is a skill published in the GitHub repository GoogleCloudPlatform/scion (2,097 stars, last pushed yesterday), licensed Apache-2.0. It adds 93 tokens to every session and 2,987 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-30.
team-creation compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| team-creationGoogleCloudPlatform/scion | Skill | 2.1k | yesterday | Apache-2.0 | A | 93 | Claude Code, Codex |
| imagegenopenai/codex | Skill | 133k | today | Apache-2.0 | A | 113 | Codex |
| playwright-climicrosoft/playwright | Skill | 99k | yesterday | Apache-2.0 | A | 19 | Claude Code |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | 4d ago | MIT | A | 200 | Claude Code, Codex |
| systematic-debuggingobra/superpowers | Skill | 313k | 3d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | today | MIT | A | 95 | Claude Code |
| chat-pet-sprite-creationmicrosoft/vscode | Skill | 195k | today | MIT | A | 53 | Claude Code, Codex |