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.

pre-build-certification - Prompt

Name: pre-build-certification
Author: KallokTherok1994

Prompt file imported from KallokTherok1994/TITANE_INFINITY (.github/prompts/pre-build-certification.prompt.md). Copyright stays with the author.

Pre-BUILD Certification

Agent: invoke pre-build-certifier for this session.

Use .github/agents/pre-build-certifier.agent.md.

Goal: Certify whether BUILD ALL is allowed.

Do not build unless:

BUILD_ALLOWED=YES

Required lifecycle:

Discover authority.
Detect canonical pipeline.
Verify worktree. 3.5. Run frontend runtime pre-build gate if frontend/runtime files changed: bash scripts/verify/prebuild-frontend-runtime-certifier.sh Stop if FRONTEND_RUNTIME_PREBUILD != PASS.
Verify instructions.
Verify agent config.
Verify toolchain.
Verify frontend.
Verify backend/Tauri/IPC/network.
Clean stale state safely.
Run pnpm run dev:tauri.
Capture DevTools Console.
Capture HTTP/Network.
Capture WebUI route proof.
Capture visible UI proof where applicable.
Run E2E/Desktop proof.
Verify runtime promotion truth.
Run AutoHeal/anti-regression.
Produce BUILD_PERMISSION_MATRIX.md.
Produce proof pack.
Return final verdict.

No build while any lane is red, unknown, partial, blocked, warning-unclassified, or missing.

# Pre-BUILD Certification > **Agent**: invoke `pre-build-certifier` for this session. Use `.github/agents/pre-build-certifier.agent.md`. Goal: Certify whether BUILD ALL is allowed. Do not build unless: ```txt BUILD_ALLOWED=YES ``` Required lifecycle: 1. Discover authority. 2. Detect canonical pipeline. 3. Verify worktree. 3.5. Run frontend runtime pre-build gate if frontend/runtime files changed: `bash scripts/verify/prebuild-frontend-runtime-certifier.sh` Stop if `FRONTEND_RUNTIME_PREBUILD` != PASS. 4. Verify instructions. 5. Verify agent config. 6. Verify toolchain. 7. Verify frontend. 8. Verify backend/Tauri/IPC/network. 9. Clean stale state safely. 10. Run `pnpm run dev:tauri`. 11. Capture DevTools Console. 12. Capture HTTP/Network. 13. Capture WebUI route proof. 14. Capture visible UI proof where applicable. 15. Run E2E/Desktop proof. 16. Verify runtime promotion truth. 17. Run AutoHeal/anti-regression. 18. Produce `BUILD_PERMISSION_MATRIX.md`. 19. Produce proof pack. 20. Return final verdict. No build while any lane is red, unknown, partial, blocked, warning-unclassified, or missing.

Install pre-build-certification 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.

{ "prompt": "# Pre-BUILD Certification\n\n> **Agent**: invoke `pre-build-certifier` for this session.\n\nUse `.github/agents/pre-build-certifier.agent.md`.\n\nGoal:\nCertify whether BUILD ALL is allowed.\n\nDo not build unless:\n\n```txt\nBUILD_ALLOWED=YES\n```\n\nRequired lifecycle:\n\n1. Discover authority.\n2. Detect canonical pipeline.\n3. Verify worktree.\n 3.5. Run frontend runtime pre-build gate if frontend/runtime files changed:\n `bash scripts/verify/prebuild-frontend-runtime-certifier.sh`\n Stop if `FRONTEND_RUNTIME_PREBUILD` != PASS.\n4. Verify instructions.\n5. Verify agent config.\n6. Verify toolchain.\n7. Verify frontend.\n8. Verify backend/Tauri/IPC/network.\n9. Clean stale state safely.\n10. Run `pnpm run dev:tauri`.\n11. Capture DevTools Console.\n12. Capture HTTP/Network.\n13. Capture WebUI route proof.\n14. Capture visible UI proof where applicable.\n15. Run E2E/Desktop proof.\n16. Verify runtime promotion truth.\n17. Run AutoHeal/anti-regression.\n18. Produce `BUILD_PERMISSION_MATRIX.md`.\n19. Produce proof pack.\n20. Return final verdict.\n\nNo build while any lane is red, unknown, partial, blocked, warning-unclassified, or missing.", "variables": [], "notes": "Decide whether BUILD ALL is allowed by routing through the pre-build certifier and emitting a build permission matrix plus proof artifacts. Mode: agent.", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/KallokTherok1994/TITANE_INFINITY", "path": ".github/prompts/pre-build-certification.prompt.md", "ref": "32395b1310b540cd16d915ddbc7cc228c92b41e8", "url": "https://github.com/KallokTherok1994/TITANE_INFINITY/blob/32395b1310b540cd16d915ddbc7cc228c92b41e8/.github/prompts/pre-build-certification.prompt.md", "key": "KallokTherok1994/TITANE_INFINITY/.github/prompts/pre-build-certification.prompt.md" } } }

pre-build-certification

About

Pre-BUILD Certification

Use it

Install pre-build-certification 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