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 commands/divyamrastogi/model-orchestration/setup-workergit clone --depth 1 https://github.com/divyamrastogi/model-orchestrationWrote 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/commands/divyamrastogi/model-orchestration/setup-worker)<a href="https://agentmods.dev/commands/divyamrastogi/model-orchestration/setup-worker"><img src="https://agentmods.dev/badge/commands/divyamrastogi/model-orchestration/setup-worker.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.00018 | $0.00514 |
| Opus 5 | $0.00009 | $0.00257 |
| Sonnet 5 | $0.00004 | $0.00103 |
| Haiku 4.5 | $0.00002 | $0.00051 |
Grade A, and why
setup-worker scanned grade A with 1 finding 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 3d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
**Ollama preset:** first check the server is up (`curl -s localhost:11434/api/version`) What it actually says
Set up one or more model workers using the orchestrating-model-workers skill (read its SKILL.md in this plugin before starting).
Arguments given: "$ARGUMENTS"
- Run
"${CLAUDE_PLUGIN_ROOT}/scripts/setup-worker.sh" presetsto load the known providers. - If no provider was specified in the arguments: ask the user which provider(s) to configure using the AskUserQuestion tool — one option per preset (label + note as description, multiSelect: true) — rather than making them type URLs. If they pick "Other", ask for the provider name and look up its Anthropic-compatible endpoint and model names in its docs (web search if needed).
- For each chosen provider, run:
"${CLAUDE_PLUGIN_ROOT}/scripts/setup-worker.sh" create <name> --provider <id>Default the worker name to the preset id unless the user gave one. Ollama preset: first check the server is up (curl -s localhost:11434/api/version) and runollama list, then ask the user which local model to map the tiers to (offer instruct/tool-capable models; warn against-mlxvariants — see the skill's local-models caveats). Pass it via--sonnet <model>and set the key yourself:printf 'ollama' | setup-worker.sh set-key <name>. - Show the user where to get the key (the preset's key_url) and exactly how to add it (the two options the script printed). NEVER ask them to paste the key into chat; if they do anyway, use it but advise rotating it afterwards.
- Once they confirm the key is in place, run
"${CLAUDE_PLUGIN_ROOT}/scripts/setup-worker.sh" finalize <name>and report the smoke-test result. If it fails, debug per the skill's traps table (stale preset model names → check the provider docs). - Offer to append the skill's
templates/delegation-rules.mdto their~/.claude/CLAUDE.mdso delegation becomes a standing behavior.
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.
- 3d ago First seen · 36 lines · 18 tokens per session scan A 78fe4715823a
setup-worker is a command published in the GitHub repository divyamrastogi/model-orchestration (4 stars, last pushed 4d ago), licensed MIT. It adds 18 tokens to every session and 514 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.