Automate and extend¶
Colossus extensions enter through explicit, inspectable boundaries. Choose the smallest mechanism that fits the capability.
| Need | Mechanism |
|---|---|
| Orchestrate bounded durable steps | Workflow |
| Add agent instructions and text resources | Skill |
| Connect a supported service or OpenAPI operation | Integration |
| Run a configured external tool server | MCP |
| Distribute executable capabilities and related assets | Pack |
| Distribute a signed set of packs and skills | Collection |
One trust model¶
Extensions do not create a parallel execution path. Their tools are candidates only after configuration, connection, verification, or trust makes them applicable. Calls still pass through access selection, policy, approval, one-use permits, sandbox enforcement, output bounds, quarantine, release, and audit.
Skills are the exception only in the sense that they never execute: they contribute instructions and bounded resources. Put executable behavior in a verified pack, configured MCP server, or integration.
Start with Your first workflow.