Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/openops-studio/vibe-driven-dev/ai-provider-selectornpx skills add OpenOps-Studio/vibe-driven-dev --skill ai-provider-selectorgit clone --depth 1 https://github.com/OpenOps-Studio/vibe-driven-devWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/openops-studio/vibe-driven-dev/ai-provider-selector)<a href="https://agentmods.dev/skills/openops-studio/vibe-driven-dev/ai-provider-selector"><img src="https://agentmods.dev/badge/skills/openops-studio/vibe-driven-dev/ai-provider-selector.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00034 | $0.01711 |
| Opus 5 | $0.00017 | $0.00856 |
| Sonnet 5 | $0.00007 | $0.00342 |
| Haiku 4.5 | $0.00003 | $0.00171 |
Grade A, and why
ai-provider-selector scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 201 lines · 34 tokens per session scan A bed3b35223d9
ai-provider-selector is a skill published in the GitHub repository OpenOps-Studio/vibe-driven-dev (1 stars, last pushed 5mo ago), with no licence file. It adds 34 tokens to every session and 1,711 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
ai-provider-selector
Recommend the best AI provider and model for a project based on its use case, performance needs, cost constraints, and current model availability via MCPs.
skill-bootstrapper
Automatically discover, recommend, and install external skills from the open skills ecosystem after user intent is captured. Orchestrates find-skills installation, discovery queries, scoring, and phased install planning.
skill-recommender
Recommend the best external coding-agent skills for the current project, explain why they fit, and optionally generate a controlled install plan.
stack-advisor
Recommend the right technology stack for a project based on type, platform, team constraints, and real-time ecosystem health via MCPs.
digital-health-clinical-asr-setup
Stage 1 of Clinical ASR Flywheel. Use when bootstrapping a cycle: NVCF+MW disclosure, NVIDIAAPIKEY check, deps install, TTS+ASR smoke test.
doc-to-lora-evaluator
Evaluate whether Doc-to-LoRA is the right path for turning documents into parametric memory, and guide a safe proof-of-concept before investing in a full plugin or training pipeline. Use when a user wants to internalize long documents, reduce repeated context costs, compare Doc-to-LoRA against RAG or long-context…