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/alphalab-ustc/ohmycode/add-providernpx skills add AlphaLab-USTC/OhMyCode --skill add-providergit clone --depth 1 https://github.com/AlphaLab-USTC/OhMyCodeWrote 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/alphalab-ustc/ohmycode/add-provider)<a href="https://agentmods.dev/skills/alphalab-ustc/ohmycode/add-provider"><img src="https://agentmods.dev/badge/skills/alphalab-ustc/ohmycode/add-provider.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.00028 | $0.00903 |
| Opus 5 | $0.00014 | $0.00451 |
| Sonnet 5 | $0.00006 | $0.00181 |
| Haiku 4.5 | $0.00003 | $0.00090 |
Grade A, and why
add-provider 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.
How it starts
The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add a New LLM Provider to OhMyCode
Connect a new LLM backend (e.g., Gemini, Ollama, DeepSeek, local models).
When to Use
- User says "add a provider", "connect to Gemini", "support Ollama"
- User wants to use a model from a new API that isn't OpenAI-compatible
Prerequisites
- Read
docs/DEVELOPMENT_GUIDE.md - Read
ohmycode/providers/base.pyto understandProviderProtocol,register_provider() - Read
ohmycode/core/messages.pyforTextChunk,ToolCallStart,TurnComplete,TokenUsage - Look at
ohmycode/providers/openai.pyas reference
Step-by-Step Guide
Step 1: Understand the Provider Protocol
Every provider must implement one method:
async def stream(
self,
messages: list[Message],
tools: list[ToolDef],
system: str,
model: str,
**kwargs,
) -> AsyncIterator[StreamEvent]:
It must yield these events in order:
TextChunk(text="...")— for each streamed text tokenToolCallStart(tool_name="...", tool_use_id="...", params={...})— for each tool callTurnComplete(finish_reason="stop"|"tool_use", usage=TokenUsage(...))— always last
Step 2: Create the Provider File
Copy templates/provider_template.py to ohmycode/providers/<name>.py.
Fill in:
__init__()— initialize the API clientstream()— handle the streaming response format of the target API
Step 3: Handle Message Conversion
Different APIs have different message formats. Key conversions:
UserMessage→ the API's user message formatAssistantMessage(withtool_calls) → the API's assistant + tool use formatToolResultMessage→ the API's tool result formatsystemparameter → some APIs put it in messages, some as a separate param
Step 4: Write Tests
Create tests/providers/test_<name>_provider.py:
import pytest
from ohmycode.providers.base import PROVIDER_REGISTRY
def test_provider_is_registered():
import ohmycode.providers.<name>
assert "<name>" in PROVIDER_REGISTRY
def test_provider_instantiation():
from ohmycode.providers.<name> import <ProviderClass>
provider = <ProviderClass>(api_key="test")
assert provider.name == "<name>"
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 111 lines · 28 tokens per session scan A 08b8a77d1838
add-provider is a skill published in the GitHub repository AlphaLab-USTC/OhMyCode (131 stars, last pushed 5mo ago), licensed MIT. It adds 28 tokens to every session and 903 once invoked, about $0.0001 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…