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.
performance-audit - Prompt - OpenSmartRoute
Promptv1.0.0
performance-audit
측정은 runtime agent, 독립적인 읽기 전용 감사는 reviewer를 사용한다. frame loop, 반복 할당, subscription, typed-array 재사용, draw call, resource ownership, visibility, culling, 시나리오 기준선을 검사한다. 측정된 사실과 추정을 구분한다.
Prompt file imported from jigglypop/gaesup-world (.codex/prompts/performance-audit.md). Copyright stays with the author.
Performance 감사
측정은 runtime agent, 독립적인 읽기 전용 감사는 reviewer를 사용한다. frame loop, 반복 할당, subscription, typed-array 재사용, draw call, resource ownership, visibility, culling, 시나리오 기준선을 검사한다. 측정된 사실과 추정을 구분한다.
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
# Performance 감사
측정은 runtime agent, 독립적인 읽기 전용 감사는 reviewer를 사용한다. frame loop, 반복 할당, subscription, typed-array 재사용, draw call, resource ownership, visibility, culling, 시나리오 기준선을 검사한다. 측정된 사실과 추정을 구분한다.
Manifest
The prompt text and its fill-in variables. Copy it or fetch it by URL from your own code.
{
"prompt": "# Performance 감사\n\n측정은 runtime agent, 독립적인 읽기 전용 감사는 reviewer를 사용한다. frame loop, 반복 할당, subscription, typed-array 재사용, draw call, resource ownership, visibility, culling, 시나리오 기준선을 검사한다. 측정된 사실과 추정을 구분한다.",
"variables": [],
"notes": "측정은 runtime agent, 독립적인 읽기 전용 감사는 reviewer를 사용한다. frame loop, 반복 할당, subscription, typed-array 재사용, draw call, resource ownership, visibility, culling, 시나리오 기준선을 검사한다. 측정된 사실과 추정을 구분한다.",
"metadata": {
"source": {
"provider": "github-codex-prompts",
"repository": "https://github.com/jigglypop/gaesup-world",
"path": ".codex/prompts/performance-audit.md",
"ref": "e5a0410276bc3e188fb7b62e9e89b952f9c036fe",
"url": "https://github.com/jigglypop/gaesup-world/blob/e5a0410276bc3e188fb7b62e9e89b952f9c036fe/.codex/prompts/performance-audit.md",
"key": "jigglypop/gaesup-world/.codex/prompts/performance-audit.md"
}
}
}
Installed into a catalogue, chosen by a router
Install performance-audit 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.