The /orchestrate skill is impressive, however the model schema is not particularly cost efficient - especially compared against this article https://cursor.com/blog/agent-swarm-model-economics - where ops 4.8 paired with composer 2.5 was the most cost effective pairing
It should be possible to define the runtime value of https://github.com/cursor/plugins/blob/main/orchestrate/skills/orchestrate/scripts/models.ts#L23 from a config file or env var (env var probably easier for cursor configuration)
e.g. I've actually had a lot of success on smaller scale tasks (e.g. not an sqlite rewrite) with grok + composer, and that's very cost effective
The
/orchestrateskill is impressive, however the model schema is not particularly cost efficient - especially compared against this article https://cursor.com/blog/agent-swarm-model-economics - where ops 4.8 paired with composer 2.5 was the most cost effective pairingIt should be possible to define the runtime value of https://github.com/cursor/plugins/blob/main/orchestrate/skills/orchestrate/scripts/models.ts#L23 from a config file or env var (env var probably easier for cursor configuration)
e.g. I've actually had a lot of success on smaller scale tasks (e.g. not an sqlite rewrite) with grok + composer, and that's very cost effective