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 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/orchestration)<a href="https://agentmods.dev/skills/jxoesneon/ciel/orchestration"><img src="https://agentmods.dev/badge/skills/jxoesneon/ciel/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/orchestration"><img src="https://agentmods.dev/badge/skills/jxoesneon/ciel/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.00016 | $0.00531 |
| Opus 5 | $0.00008 | $0.00266 |
| Sonnet 5 | $0.00003 | $0.00106 |
| Haiku 4.5 | $0.00002 | $0.00053 |
Grade A, and why
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 9d 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.
What it actually says
CIEL ADAPTATION: Orchestration
This skill provides CIEL's high-level planning and coordination engine. It transforms complex objectives into actionable, step-by-step construction plans.
Integration Context
Adapted from ~/.agents/skills/blueprint/. This version integrates CIEL's Council of Five for plan review, ensuring architectural alignment and risk mitigation.
The Orchestration Pipeline
1. Research
Analyze the workspace, existing infrastructure, and constraints. CIEL uses its memory graph to ensure context continuity.
2. Design
Decompose the objective into discrete, "PR-sized" steps. Assign dependencies, parallel workflows, and model tiers.
3. Draft
Generate a self-contained Markdown plan. Each step must be executable "cold" by any sub-agent.
4. Council Review (Ciel Core)
The draft plan is submitted to the Council of Five for evaluation:
- Coherence: Does the plan follow our architectural standards?
- Capability: Are the steps technically sound and sufficient?
- Safety: Are there risks to production or system integrity?
- Efficiency: Is the parallelism optimized?
- Evolution: Is there a clear path for verification and rollback?
5. Execution & Mutation
Orchestrate the execution of steps. If obstacles arise, use the Mutation Protocol to adapt the plan mid-stream.
Usage
Use this skill when:
- A task requires more than 3 tool calls or spans multiple sessions.
- Coordinating work across multiple parallel sub-agents.
- Building a roadmap for large-scale refactors or new features.
Original Documentation preserved at source.
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.
- 9d ago First seen · 77 lines · 16 tokens per session scan A fdab4885ec04
orchestration is a skill published in the GitHub repository jxoesneon/Ciel (1 stars, last pushed 5d ago), licensed Apache-2.0. It adds 16 tokens to every session and 531 once invoked, about $0.0001 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
surge
Use when a user provides a PRD, spec, or detailed requirements document and needs a full project delivered through iterative expert orchestration — multi-round analyze/research/design/implement/QA cycles with convergence detection. NOT for: single-file edits, quick prototypes, simple Q&A, or tasks without a written…
ai-native-software-dev
Use when the user asks to build, change, modernize, or reconstruct non-trivial software with an AI-native workflow, including greenfield development, work in an existing codebase, or authorized reference-based product reconstruction; also use when lifecycle planning, architecture, implementation, testing, review…
Code Quality Review
Conduct a comprehensive code quality review focused on clean code, architecture, and project standards.
redpolicy-guide
An editorial policy for turning webinar transcripts into self-contained guides. A transcript is a written record of spoken material, while a self-contained guide can be understood without watching the webinar.
write-overview
A workflow for researching and writing a review essay about a project topic when no finished source text exists. It gathers the facts, studies example essays when available and produces the article in a project output folder.
redpolicy-article
An editorial guide for writing comparison articles about services, tools, and products. It defines a consistent entry format covering the name, link, price, description, and notable features.