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 Alexander-Tyagunov/magician --skill orchestrategit clone --depth 1 https://github.com/Alexander-Tyagunov/magicianWrote 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/alexander-tyagunov/magician/orchestrate)<a href="https://agentmods.dev/skills/alexander-tyagunov/magician/orchestrate"><img src="https://agentmods.dev/badge/skills/alexander-tyagunov/magician/orchestrate/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/alexander-tyagunov/magician/orchestrate"><img src="https://agentmods.dev/badge/skills/alexander-tyagunov/magician/orchestrate.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.00183 |
| Opus 5 | $0.00020 | $0.00092 |
| Sonnet 5 | $0.00008 | $0.00037 |
| Haiku 4.5 | $0.00004 | $0.00018 |
Grade A, and why
orchestrate 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 11d 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
$orchestrate — Codex Adapter
Read ../../references/codex-adapter.md, then read ../../../skills/orchestrate/SKILL.md and follow the source skill through that Codex adapter. Keep the source skill's gates, safety checks, and completion criteria.
Translate source agent teams and magician:* profiles into available generic Codex agents with self-contained prompts. Dispatch only independent blueprint nodes in parallel, collect results through normal agent completion/waiting, and run sequential nodes locally or in order. Do not invent agent-closing or native workflow APIs. Commits are optional side effects: stage only task-owned files and require the user's commit authorization.
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.
- 11d ago First seen · 11 lines · 41 tokens per session scan A 3ee6d6a2bc16
orchestrate is a skill published in the GitHub repository Alexander-Tyagunov/magician (14 stars, last pushed 10d ago), licensed MIT. It adds 41 tokens to every session and 183 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-08-30.
Other skills, from other repositories
daily-briefing
Search for today's latest AI news and create/update a comprehensive briefing in Notion, with optional Obsidian vault publishing for graph visualization.
custom-brief
Deep-research a specific topic and produce a comprehensive news-focused briefing with optional Notion/Obsidian/Teams/Slack publishing.
eval-dashboard
Build the interactive offline eval dashboard (eval/dashboard/index.html) — Chart.js trend, axis radar, composite histogram, per-card stacked bars, sortable card table. Use when the user wants to "see eval results", "open dashboard", "visualize quality", or "compare cards".
eval-drift
Detect quality drift in published briefings by comparing the trailing-7d median composite score against the trailing-30d median (MAD-scaled). Use when the user asks to "check drift", "compare last week to baseline", or "is briefing quality slipping".
eval-regression
Re-judge every pinned golden card in eval/golden/ and fail if any composite has dropped more than 0.5 points vs its baseline. Use when the user asks to "run regression", "check golden set", or wants CI-style quality gating after a prompt or judge change.
eval-report
Emit a Markdown weekly digest of briefing quality scores (coverage, composite stats, axis medians, per-day table). Use when the user asks for a "weekly report", "eval summary", or "quality digest" for a specific date range.