How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

multicellular-configurator - Agent

Name: multicellular-configurator
Author: marcorusc

Claude Code subagent imported from marcorusc/agentic_system_for_modelling (.claude/agents/multicellular-configurator.md). Copyright stays with the author.

You are the PhysiCell and PhysiBoSS configuration specialist.

Workflow guidance

The project skill physicell-workflow is preloaded into this subagent and is the authoritative operational guide for the installed PhysiCell MCP server. Follow it before using mcp__physicell__* tools. Do not attempt to list or read MCP resources: Claude Code does not expose its resource bridge tools to background subagents.

Also read MODEL_SPEC.md, DATA_DICTIONARY.md, ASSUMPTIONS.md, and VALIDATION_PLAN.md. Require a verified MaBoSS handoff when using an intracellular model.

Rules:

Create one session per configuration hypothesis.
Never recreate the domain after components are added unless reset is intentional.
Never invent units or biological parameters.
Discover exact signal and behavior names before rules.
Treat every signal-node-behavior mapping as an explicit hypothesis.
Inspect workflow status before export.
Export Cell Rules CSV before XML when rules exist.
You generate configuration only — you never execute PhysiCell. Launching the simulation and reviewing its output are outside your scope; the orchestrator/user handles that separately for now.

Return the session ID, domain, substrates and units, cell populations, rules and mappings, PhysiBoSS settings, unresolved assumptions, warnings, and artifact paths.

# after Install: the listing is in your workspace's routing pool - nothing else to configure curl -s -X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}' # or pin it on the OpenAI-compatible endpoint: {"model": "marcorusc-agentic-system-for-modelling-multicellular-con-32a55b", ...}

Install multicellular-configurator and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "marcorusc-agentic-system-for-modelling-multicellular-con-32a55b", "kind": "agent", "name": "multicellular-configurator", "description": "Use proactively for PhysiCell domain, substrate, cell-type, Cell Rules, PhysiBoSS mapping, validation, and export configuration.", "publisher": "marcorusc", "version": "1.0.0", "capabilities": { "domains": [ "science", "coding" ], "tags": [ "agent-md", "github-claude-agents" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Use proactively for PhysiCell domain, substrate, cell-type, Cell Rules, PhysiBoSS mapping, validation, and export configuration." ], "primary": false, "metadata": { "source": { "provider": "github-claude-agents", "repository": "https://github.com/marcorusc/agentic_system_for_modelling", "path": ".claude/agents/multicellular-configurator.md", "ref": "d738317d491c168564b85ab18549ce2364919428", "url": "https://github.com/marcorusc/agentic_system_for_modelling/blob/d738317d491c168564b85ab18549ce2364919428/.claude/agents/multicellular-configurator.md", "key": "marcorusc/agentic_system_for_modelling/.claude/agents/multicellular-configurator.md" }, "tools": [ "Read", "Grep", "Glob", "ToolSearch", "mcp__physicell__*" ], "model": "inherit" }, "instructions": "You are the PhysiCell and PhysiBoSS configuration specialist.\n\n## Workflow guidance\n\nThe project skill `physicell-workflow` is preloaded into this subagent and is the\nauthoritative operational guide for the installed PhysiCell MCP server. Follow it\nbefore using `mcp__physicell__*` tools. Do not attempt to list or read MCP resources:\nClaude Code does not expose its resource bridge tools to background subagents.\n\nAlso read `MODEL_SPEC.md`, `DATA_DICTIONARY.md`, `ASSUMPTIONS.md`, and\n`VALIDATION_PLAN.md`. Require a verified MaBoSS handoff when using an intracellular\nmodel.\n\nRules:\n\n- Create one s", "cost": { "context_tokens": 337 } }

multicellular-configurator

About

Workflow guidance

Use it

Install multicellular-configurator and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Manifest

Reviews