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 autonomous-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/autonomous-orchestration)<a href="https://agentmods.dev/skills/jxoesneon/ciel/autonomous-orchestration"><img src="https://agentmods.dev/badge/skills/jxoesneon/ciel/autonomous-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/autonomous-orchestration"><img src="https://agentmods.dev/badge/skills/jxoesneon/ciel/autonomous-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.00025 | $0.00504 |
| Opus 5 | $0.00013 | $0.00252 |
| Sonnet 5 | $0.00005 | $0.00101 |
| Haiku 4.5 | $0.00003 | $0.00050 |
Grade A, and why
autonomous-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 7d 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: Autonomous Orchestration (Fleets & Missions)
This skill formalizes the execution of multi-step, multi-agent workflows. it prioritizes isolation, structured reporting, and persistent scheduling.
The Fleet Pattern (DevFleet)
- Mission DAG: Break complex requests into a Directed Acyclic Graph (DAG) of missions.
- Isolation: Each agent MUST run in an isolated git worktree with dedicated tooling.
- Auto-Dispatch: Missions with met dependencies auto-start. missions with blocked dependencies queue.
- Merge Protocol: Missions auto-merge on success; conflict resolution is a manual or dedicated "Conflict Solver" mission.
Scheduled Operations (Crons)
- Persistence: Use native scheduled tasks for recurring monitoring (e.g., Daily standup at 9 AM).
- Session Isolation: Crons run in isolated sessions. use project memory for cross-session context.
- Error Handling: Every cron prompt MUST include instructions for handling failures (e.g., "If tests fail, post log to memory and alert user").
Reporting & Status
- Dashboard: Use
get_dashboard()to monitor slot usage and recent activity. - Missions: Every mission MUST produce a
MISSION_REPORT.md(Files changed, Tests run, Next steps).
Anti-Patterns
- Circular Missions: Creating a dependency loop between agents.
- Shared Worktrees: Running two independent agents in the same directory (causes race conditions).
- Amnesiac Crons: Running a daily task that doesn't read the previous day's result from memory.
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.
- 7d ago First seen · 50 lines · 25 tokens per session scan A fc34cc6c2f23
autonomous-orchestration is a skill published in the GitHub repository jxoesneon/Ciel (1 stars, last pushed 3d ago), licensed Apache-2.0. It adds 25 tokens to every session and 504 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
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.
delivery
Fecha o ciclo de entrega local — build check, bump semântico, changelog e commit convencional. Deploy remoto somente sob a condição dupla do Ops. Use para "finalizar tarefa", "fazer release" ou "publicar versão".
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".
gitnexus-cli
Use when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: "Index this repo", "Reanalyze the codebase", "Generate a wiki".
github-release-pr-writer
Draft or update GitHub release pull request descriptions from verified tags, commits, merged pull requests, and the release diff. Use when a PR prepares a version, aligns release metadata, promotes a prerelease, or needs a reviewer-focused release summary, exact change inventory, breaking-change section, or migration…
codex-review
Professional code review with auto CHANGELOG generation, integrated with Codex AI.