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 jxoesneon/Ciel --skill gastown-orchestrationgit clone --depth 1 https://github.com/jxoesneon/CielWrote 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/jxoesneon/ciel/gastown-orchestration)<a href="https://agentmods.dev/skills/jxoesneon/ciel/gastown-orchestration"><img src="https://agentmods.dev/badge/skills/jxoesneon/ciel/gastown-orchestration/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/jxoesneon/ciel/gastown-orchestration"><img src="https://agentmods.dev/badge/skills/jxoesneon/ciel/gastown-orchestration.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.00041 | $0.01159 |
| Opus 5 | $0.00020 | $0.00580 |
| Sonnet 5 | $0.00008 | $0.00232 |
| Haiku 4.5 | $0.00004 | $0.00116 |
Grade A, and why
gastown-orchestration 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 8d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CIEL ADAPTATION: Gas Town Orchestration (CLI Toolchain)
This skill adapts the Gas Town CLI toolchain (gt/bd) into Ciel's vocabulary. It provides a CLI-driven alternative to Ciel's internal fleet model — where autonomous-orchestration uses Ciel-native worktrees and missions, gastown uses external process spawning, bead-based work tracking, and mail-triggered patrols. Ciel's risk classifier gates subprocess spawning as mid→LLM_JUDGE or high→Council.
Core Vocabulary (Ciel Translation)
- Bead (
bd): A tracked work unit. Ciel equivalent: a mission task ticket. - Convoy: A batch of related beads. Ciel equivalent: a mission DAG node group.
- Rig: A registered project workspace (GitHub repo). Ciel equivalent: an isolated worktree target.
- Polecat: Ephemeral worker spawned per-task, vanishes on completion. Ciel equivalent: a one-shot sub-agent.
- Crew: Persistent named worker with ongoing sessions. Ciel equivalent: a long-lived fleet agent.
- Hook: Where work lands for a worker. GUPP (Gas Town Universal Propulsion Principle): if hook has work, run it.
- Molecule: A workflow unit that survives crashes — any worker can resume where another left off.
- Patrols: Witness (watches for stuck workers), Refinery (merges completed work), Mayor (coordinates rigs).
CLI Command Patterns
Engine Control: gt up (start), gt down (graceful stop), gt status (overview)
Work Management: gt sling <bead> <rig> (assign work), gt convoy list, gt hook
Workers: gt polecat list, gt crew list, gt peek <agent>, gt nudge <agent> "msg"
Diagnostics: gt doctor (health check), gt doctor --fix (auto-repair), bd doctor, gt feed (activity stream)
Beads: bd list, bd show <id>, bd sync, bd create --title "..."
Refinery: gt refinery start, gt refinery status, gt refinery queue
Patrol Activation: gt mail send <rig>/witness -s "Patrol" -m "Process completed work"
Lifecycle Management
- Install:
go install .../gt@latest+go install .../bd@latest; verify withgt doctorANDbd doctor. - Add Rig: Register a project; verify patrols exist via
gt doctor --fix. - Create Work:
bd create --title "..."→ bead ID assigned. - Sling:
gt sling <bead> <rig>→ polecat spawns, work lands on hook, GUPP executes. - Monitor:
gt peek <agent>,gt feed; Witness patrols detect stuck workers. - Merge: Refinery processes completed work → code lands on main.
- Shutdown:
gt downfor graceful stop.
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.
- 8d ago First seen · 71 lines · 41 tokens per session scan A dc0aa58b99b2
gastown-orchestration is a skill published in the GitHub repository jxoesneon/Ciel (1 stars, last pushed 4d ago), licensed Apache-2.0. It adds 41 tokens to every session and 1,159 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-09-03.
Other skills, from other repositories
factory-handoff
Hand one exact agent-ready ticket to the central Factory runtime over the configured SSH forced-command boundary. Use when an operator asks to hand off an existing ticket or a prose request instead of implementing it in the current session.
ticket-spec
Turn a raw Linear Triage ticket into a fully specified ai:agent-ready one by exploring the codebase. Use when specifying, refining, or promoting tickets, or when asked why a ticket isn't dispatchable.
feature-flow
Cria o diretório canônico da task (docs/todo/NNN-slug/), a branch e o scaffolding inicial. Use para "criar feature", "iniciar tarefa" ou "abrir task".
task-tracker
Escaneia docs/todo/ reportando o Status de cada task e arquiva em docs/done/ somente as entregues. Use para "verificar tasks", "o que está pendente" ou "arquivar concluídas".
autonomous-project-manager
This is the 'Master Blueprint' for long-running autonomous tasks. Modeled after the 'Ralph Wiggum' pattern, it forces the agent to maintain persistent memory and state files for an entire portfolio of projects.
feature-retirement-comms-planner
Identifies users dependent on a feature being removed. Drafts a timeline of 3 emails: 'Heads up', 'Alternative Workflows', and 'Final Reminder'.