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 convoy-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/convoy-orchestration)<a href="https://agentmods.dev/skills/jxoesneon/ciel/convoy-orchestration"><img src="https://agentmods.dev/badge/skills/jxoesneon/ciel/convoy-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/convoy-orchestration"><img src="https://agentmods.dev/badge/skills/jxoesneon/ciel/convoy-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.00033 | $0.00796 |
| Opus 5 | $0.00016 | $0.00398 |
| Sonnet 5 | $0.00007 | $0.00159 |
| Haiku 4.5 | $0.00003 | $0.00080 |
Grade A, and why
convoy-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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CIEL ADAPTATION: Convoy Orchestration (Dependency-Graph Distribution)
This skill provides dependency-graph-based task distribution for agent crews. While ciel-swarm-orchestration focuses on automatic task decomposition and parallel fan-out, convoy-orchestration adds explicit dependency modeling — you define which tasks block which, and the system routes work accordingly. Use this when tasks have complex interdependencies that automatic decomposition cannot capture.
When to Activate
- A project is too large for one agent session and tasks have explicit dependencies.
- You need coordinated effort across multiple parallel work streams with ordering constraints.
- Work needs tracking across distributed agents with checkpoint-based coordination.
- You are managing a critical path where some tasks block everything downstream.
Orchestration Patterns
- Parallel Map: Same task on different inputs — fan-out → process → fan-in.
- Pipeline: Sequential stages — Stage 1 → Stage 2 → Stage 3.
- Reduce: Aggregate parallel results — distribute → process → collect → combine.
- Tree: Hierarchical decomposition — parent → children → grandchildren.
- Mesh: Interdependent tasks — dependency graph with partial ordering.
Workflow
- Decompose: Break project scope into parallelizable work units with clear completion criteria.
- Define Dependencies: Map which tasks need what — identify the critical path.
- Assign: Distribute tasks across available agent capacity, respecting dependency order.
- Execute & Monitor: Track progress, handle blockers, checkpoint frequently.
- Synthesize: Combine outputs into a coherent deliverable; run Council coherence check.
Dependency Management
- Minimize dependencies to maximize parallelization.
- Identify the critical path early — these tasks block everything.
- Handle failures gracefully: retry, reassign, or find workaround.
- Checkpoint frequently — don't lose progress on agent failure.
- Version intermediate results for rollback to last known good state.
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 · 80 lines · 33 tokens per session scan A 346885dd7d00
convoy-orchestration is a skill published in the GitHub repository jxoesneon/Ciel (1 stars, last pushed 4d ago), licensed Apache-2.0. It adds 33 tokens to every session and 796 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'.