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.

Qore - Skill - OpenSmartRoute

Name: Qore
Author: ganeshkumarchalla

Imported from ganeshkumarchalla/Qore (AGENTS.md). Install upstream with npx skills add ganeshkumarchalla/Qore. Copyright stays with the author.

QORE Workspace Security & Agent Guidelines

This project implements strict multi-agent security and privacy protocols. All agents, automated workflows, and developer tools operating within c:\Users\ganes\OneDrive\QORE must adhere to these policies.

1. Zero-Exposure Secret Policy

Never Output Secrets: Never print, log, return, or include contents of .env, API keys (GEMINI_API_KEY, etc.), bearer tokens, private keys, or passwords in chat responses, error messages, logs, or reports.
Redaction Mandatory: Any tool output or report that touches secrets must display redacted masks (e.g. AIzaSy...[REDACTED]).
Client/Frontend Isolation: Never place backend API keys or secrets in frontend/ files or prefix them with VITE_. In Vite, VITE_* environment variables are baked into static client bundles sent to browsers. All AI and sensitive requests must route through the backend (backend/qore/).

2. File Safety & Version Control

Ignore Protection: Ensure .env, .env.*, certificates (*.pem, *.key), databases (*.db, *.sqlite*), and credential files are strictly listed in .gitignore.
No Accidental Staging: Before committing or sharing files, verify untracked sensitive files are not staged or exposed.
Temporary & Backup Files: Clean up and ignore editor swap files (*.swp), backups (*.bak), and system metadata (.DS_Store, Thumbs.db).

3. IDE & Environment Hardening

Workspace Trust: Maintain active workspace trust (security.workspace.trust.enabled: true) in .vscode/settings.json.
Search & Index Exclusion: Sensitive files (.env*, .venv/, credentials) must be excluded from IDE file watchers and search indexes.
Telemetry Disabled: Ensure editor telemetry is disabled to prevent accidental diagnostic data transmission.

4. Multi-Agent Automated Security Auditing

Run the security audit engine at scripts/security_checker.py using the project's Python virtual environment:
```
& "C:\Users\ganes\OneDrive\QORE\.venv\Scripts\python.exe" scripts/security_checker.py --check
```
Automated audit reports are generated under evidence/security_report.md and evidence/security_report.json.

5. Frontend Quality, UI Resilience & Multi-Agent Guidelines

All agents and subagents modifying UI, styles, or frontend code must strictly adhere to docs/FRONTEND_AGENT_GUIDELINES.md.

Run the frontend health audit engine using the project's Python virtual environment:

& "C:\Users\ganes\OneDrive\QORE\.venv\Scripts\python.exe" scripts/frontend_auditor.py

Automated frontend health reports are generated under evidence/frontend_health_report.md and evidence/frontend_health_report.json.
Subagents must consult the Frontend Autonomous Agent's standards before modifying components, state structures, or API contracts.

Install Qore 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": "ganeshkumarchalla-qore-qore", "kind": "skill", "name": "Qore", "description": "This project implements strict multi-agent security and privacy protocols. All agents, automated workflows, and developer tools operating within `c:\\Users\\ganes\\OneDrive\\QORE` must adhere to these policies.", "publisher": "ganeshkumarchalla", "version": "1.0.0", "capabilities": { "domains": [ "coding", "observability" ], "tags": [ "skill-md", "github-agents" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "This project implements strict multi-agent security and privacy protocols. All agents, automated workflows, and developer tools operating within `c:\\Users\\ganes\\OneDrive\\QORE` must adhere to these policies." ], "primary": false, "metadata": { "source": { "provider": "github-agents", "repository": "https://github.com/ganeshkumarchalla/Qore", "path": "AGENTS.md", "ref": "1c238ccb5570704a3ff558787f9b05a16e909543", "url": "https://github.com/ganeshkumarchalla/Qore/blob/1c238ccb5570704a3ff558787f9b05a16e909543/AGENTS.md", "key": "ganeshkumarchalla/Qore/AGENTS.md" } }, "instructions": "# QORE Workspace Security & Agent Guidelines\n\nThis project implements strict multi-agent security and privacy protocols. All agents, automated workflows, and developer tools operating within `c:\\Users\\ganes\\OneDrive\\QORE` must adhere to these policies.\n\n---\n\n## 1. Zero-Exposure Secret Policy\n* **Never Output Secrets**: Never print, log, return, or include contents of `.env`, API keys (`GEMINI_API_KEY`, etc.), bearer tokens, private keys, or passwords in chat responses, error messages, logs, or reports.\n* **Redaction Mandatory**: Any tool output or report that touches secrets must display redac", "cost": { "context_tokens": 721 } }

Qore

About

QORE Workspace Security & Agent Guidelines

1. Zero-Exposure Secret Policy

2. File Safety & Version Control

3. IDE & Environment Hardening

4. Multi-Agent Automated Security Auditing

5. Frontend Quality, UI Resilience & Multi-Agent Guidelines

Install Qore 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

Use it

Manifest

Reviews