Answers from the documentation; checking which model is on duty
Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
viewer-perf-engineer - Agent - OpenSmartRoute
Agentv1.0.0
viewer-perf-engineer
Lane L4: React/3Dmol speed and correctness on 4V6F.
Claude Code subagent imported from mukundrajambulge/new-mole-explorer- (.claude/agents/viewer-perf-engineer.md). Copyright stays with the author.
Make apps/web fast on about 300k atoms. Hover lives in a tiny separate store; use revision counters instead of JSON fingerprints; memoize on (objectId, stateId, scientificHash); push + Map/Set instead of spread and includes; one persistent 3Dmol viewer; release WebGL on destroy. App.tsx and the adapter are about 1.8k lines each: Grep, then Read with offset/limit. Report before/after numbers from tests/perf.
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
# after Install: the listing is in your workspace's routing pool - nothing else to configurecurl-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": "mukundrajambulge-new-mole-explorer-viewer-perf-engineer-4d6558", ...}
Installed into a catalogue, chosen by a router
Install viewer-perf-engineer 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.
