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 agentmods add skills/matteblack9/coding-agent-fabric/setup-orchestratornpx skills add matteblack9/coding-agent-fabric --skill setup-orchestratorgit clone --depth 1 https://github.com/matteblack9/coding-agent-fabricWrote 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/matteblack9/coding-agent-fabric/setup-orchestrator)<a href="https://agentmods.dev/skills/matteblack9/coding-agent-fabric/setup-orchestrator"><img src="https://agentmods.dev/badge/skills/matteblack9/coding-agent-fabric/setup-orchestrator.svg" alt="Measured on agentmods" 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 | $0.00025 | $0.00933 |
| Opus 5 | $0.00013 | $0.00466 |
| Sonnet 5 | $0.00005 | $0.00187 |
| Haiku 4.5 | $0.00003 | $0.00093 |
Grade A, and why
setup-orchestrator 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 4d 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
setup-orchestrator
When To Use
- The user wants to install, bootstrap, repair, or reconfigure the orchestrator root
orchestrator.yaml,start-orchestrator.sh,AGENTS.md, orCLAUDE.mdare missing or stale- The team wants to change default runtimes, channel enablement, or workspace registry settings
Runtime Adaptation
claudeRead this file first, then honor existingCLAUDE.mdand.claude/memory if present.cursorRead this file first, then apply.cursor/rules,AGENTS.md,CLAUDE.md, and legacy.cursorrulesas additional repo rules.codexTreat this file plusAGENTS.mdas the primary procedure. Do not assume slash-command support.opencodeRead this file first, then applyAGENTS.mdplus anyopencode.jsonor.opencode/skills/overrides that already exist.
Operating Rules
- Work from the orchestrator repository root
- Prefer the setup TUI instead of editing
orchestrator.yamlby hand unless the user explicitly asks for manual edits - Present auto-detected values as numbered choices when asking the user to confirm them
- If dependencies are missing, install or repair them before launching the TUI
- Do not overwrite an existing config blindly; inspect current files first and explain what will change
Procedure
1. Preflight
- Verify that this repository contains
setup.sh,orchestrator/setup_tui.py, andtemplates/ - Check whether
.venv/,node_modules/, and required CLIs already exist - If dependencies are missing or broken, run
./setup.sh - Inspect current orchestrator assets if they already exist:
orchestrator.yamlstart-orchestrator.shAGENTS.mdCLAUDE.mdopencode.jsonand.opencode/when OpenCode is in use
2. Launch Setup
Run:
.venv/bin/python -m orchestrator.setup_tui
Let the TUI classify the current folder as one of:
- existing orchestrator root
- new orchestrator candidate
- single workspace that should be wrapped by a new orchestrator root
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.
- 4d ago First seen · 118 lines · 25 tokens per session scan A 9fa88eb007ae
setup-orchestrator is a skill published in the GitHub repository matteblack9/coding-agent-fabric (2 stars, last pushed 5mo ago), licensed MIT. It adds 25 tokens to every session and 933 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…