add-provider
Skill416 starsChanged 31 days agoMITView on GitHub
Add a new inference provider to genai-prices, including provider data, matching, usage extractors, update automation, cassettes, agentic checks, generated artifacts, and Python/JavaScript/Go parity tests. Use for a new provider, not a new model on an existing provider.
18 other projects use a version of this.
Adopted by
Most recently taken up by
- RonenMars/threadbase-mobiletheir own version, first seen Nov 15, 2026
- SDSLeon/lightcodetheir own version, first seen Nov 8, 2026
- Porabuild/Poracodetheir own version, first seen Nov 8, 2026
- agentconfig/agentconfig.orgtheir own version, first seen Nov 8, 2026
- VincentShipsIt/meterbar.devtheir own version, first seen Nov 6, 2026
- tddworks/ClaudeBartheir own version, first seen Nov 3, 2026
Used with
Projects with it also use add-tool, release-notes and 2 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MicrosoftSkilladd-tool
Add a new tool to PilotSwarm. Covers defining the tool with defineTool(), registering it on the worker (worker-level or per-session), referencing it from the client via toolNames, and adding an integration test.
Also in 3 projects that use this
Microsoft AzureSkillrelease-notes
Author and update release notes for Azure App Configuration libraries and providers. USE FOR: write release notes, add release note entry, update release notes, draft release notes, new version release notes, format release notes. DO NOT USE FOR: generating changelogs from git history, writing internal engineering notes.
Also in 3 projects that use this
SentrySkillcommit
Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.
Also in 3 projects that use this
MicrosoftSkillrelease
Use ONLY when the user explicitly asks to cut/publish a Huabu desktop release or tag a version. Performs an outward action — bumps the version in apps/desktop/package.json, commits + annotated-tags vX.Y.Z, and pushes the branch + tag. That tag push auto-builds the macOS/Windows installers and publishes a GitHub Release. Provides `status`, `bump`, `tag-push`, and a one-command `run` (bump → tag-push).
Also in 3 projects that use this
Other versions18 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 18
- ThinkInAIXYZ/deepchat★ 6.4ksame name
- tddworks/ClaudeBar★ 1.6ksame name
- Porabuild/Poracode★ 121same name
- SDSLeon/lightcode★ 121same name
- agent-cli-framework/aclif★ 20same name
- hyhmrright/StockAI★ 14same name
- VincentShipsIt/meterbar.dev★ 12same name
- yerdaulet-damir/vibe-coding-rules★ 10same name
- kiminmonaco/ClaudeBar★ 8same name
- agentconfig/agentconfig.org★ 7same name
8 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository2 other files it gives its agents.
- AGENTS.mdAGENTS.md
- add-price-modelSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
20 rules. 0 are common, 9 are distinctive, and 11 are very specific to this project.
0
Common
Most of the 15 edited versions we read keep these.
9
Distinctive
This author's own choices. Worth a look.
11
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 8
Add the provider as a complete, maintainable integration.
- Distinctive: line 12
Use the provider's official pricing page and model catalog.
- Very specific: line 14
Read prices/units.yml before mapping prices.
- Very specific: line 23
Create prices/providers/<provider>.yml.
- Very specific: line 36
use the exact API model ID as the canonical id
- Distinctive: line 37
add precise aliases without creating matches against sibling models
- Distinctive: line 44
Keep models sorted by ID. Use names and context windows from official documentation when available.
- Distinctive: line 51
Add provider extractors for flavors that report usage.
- Distinctive: line 60
If an API response does not report usage, leave that flavor unsupported and document the limitation instead of inventing a mapping.
- Very specific: line 65
Every provider needs a way to update its prices automatically.
- Very specific: line 69
Add prices/src/prices/source_<provider>.py, following source_novita.py (JSON) or source_cloudflare.py (Markdown):
- Very specific: line 85
Test the real HTTP boundary with @pytest.mark.vcr, recorded with cassetter.
- Distinctive: line 92
Use compact synthetic inputs only for pure parser and update-behavior tests.
- Very specific: line 103
Add the YAML path to create-pull-request.allowed-files in both .github/workflows/agentic-price-check.md and …
- Very specific: line 106
Update the hard-coded provider count in .github/workflows/agentic-price-check.md and .github/workflows/AGENTIC_PRICE_CHECK.md.
- Distinctive: line 119
Add focused Python, JavaScript and Go tests for:
- Distinctive: line 124
every usage extractor flavor
- Very specific: line 127
Put the Go tests in packages/go/api_test.go, which runs against the bundled provider data.
- Very specific: line 130
Run make build after every provider-data edit.
- Very specific: line 131
Never hand-edit those outputs or tests/dataset/usages.json.
“Common” is measured: kept by at least 6 in 10 of the 15 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Add a provider
Add the provider as a complete, maintainable integration. Read AGENTS.md before editing. Preserve unrelated worktree changes.
Establish the supported scope
Use the provider's official pricing page and model catalog. Record the exact source URLs.
Read prices/units.yml before mapping prices. Include only billing units represented by the current published contract. Do not
add a unit to make a provider fit because that is a v3 contract change. Explain excluded model categories in the provider's
price_comments.
Decide whether the official source is a complete catalog or only a pricing page. This determines whether missing models can be treated as potential removals.
Author the provider YAML
Create prices/providers/<provider>.yml. Never edit generated artifacts directly.
Cover these fields when they apply:
id,name, and officialpricing_urlsapi_patternfor the provider's actual API hosts and pathsprovider_matchfor common provider identifiersmodel_matchonly when the provider owns an unambiguous model-ID namespacefallback_model_providersonly when another provider's prices are intentionally inheritedprice_commentsfor free allowances, unsupported units, regional differences, or other calculation boundaries
For each supported model:
- use the exact API model ID as the canonical
id - add precise aliases without creating matches against sibling models
- map official rates to the correct units, such as
_mtok,_kcount, or_mchars - include cache, reasoning, modality, request, and tool rates when represented by the unit registry
- set
prices_checkedto the verification date - preserve historical price changes with dated conditional prices instead of overwriting old rates
- mark officially deprecated models without inferring removal from an incomplete source
Keep models sorted by ID. Use names and context windows from official documentation when available.
Add usage extraction
Inspect recorded or documented response bodies for every supported API flavor. Do not assume that an OpenAI-compatible endpoint has the same response as the provider's native endpoint.
Add provider extractors for flavors that report usage. Extract the model when the response includes it. When the response omits
the model, return the usage with a nullable model so callers can provide the request model during price calculation. Map cached
tokens separately. Any extractor that maps completion_tokens must also map the provider's reasoning-token breakdown to
output_reasoning_tokens. Test each flavor through the public Python, JavaScript and Go extraction APIs.
A caller that doesn't pass a flavor asks for default, so default, if the provider has one, reads its own API. Give every other
API the provider serves, including another company's API it passes along, its own flavor name. See the api_flavor bullet in
AGENTS.md for an example.
If an API response does not report usage, leave that flavor unsupported and document the limitation instead of inventing a mapping.
Add an automatic price update
Every provider needs a way to update its prices automatically. Look for an official source a script can read without
credentials, in this order: a pricing API or /v1/models response with prices, a Markdown docs page (.md, llms.txt), then
JSON embedded in the official pricing page. Treat an HTML fallback served for a .md URL as unreadable.
Add prices/src/prices/source_<provider>.py, following source_novita.py (JSON) or source_cloudflare.py (Markdown):
- fetch with
httpx2and parse prices asDecimal - return
ModelInfoentries from a publicparse_*function and write them withProviderYaml.upsert_models, which adds new models, appends changed rates as dated conditional prices, and keeps curated keys the source does not report - emit only the keys the source reports, and parse tiers when the source has them instead of flattening them
- set a
MIN_MODEL_COUNTso an empty or truncated response refuses to write - fail loudly when the source is unreadable or changes shape
Expose get_<provider>_prices through prices.__main__. Add <provider>-get to Makefile, include it in get-all-prices,
and add <provider> to the matrix.importer list in .github/workflows/update-prices.yml, which runs every importer hourly
and keeps one rolling PR.
Pin tests that assert the provider's current rates to an explicit timestamp. Otherwise the first hourly rate change breaks CI on the rolling PR.
Test the real HTTP boundary with @pytest.mark.vcr, recorded with cassetter. Record the official response, inspect the
cassette, commit it, and prove replay with:
uv run pytest tests/test_source_<provider>.py --record-mode=noneUse compact synthetic inputs only for pure parser and update-behavior tests. Do not replace the external request with a hand-written HTTP mock.
A provider without an importer is the exception. If no source a script can read exists, list the URLs you checked in the PR and rely on agentic monitoring alone.
Add agentic monitoring
The weekly agentic check is the fallback for what an importer cannot see: announced future prices, promotions, and new units
or tiers. Add the provider to .github/agentic-price-check-providers.yml with its YAML path, exact official sources, supported
scope, and unit-mapping notes. Add every source domain to network.allowed in .github/workflows/shared/price-check-network.md.
Add the YAML path to create-pull-request.allowed-files in both .github/workflows/agentic-price-check.md and
.github/workflows/agentic-model-price-check.md, or targeted model checks cannot open a PR for the provider.
Update the hard-coded provider count in .github/workflows/agentic-price-check.md and
.github/workflows/AGENTIC_PRICE_CHECK.md. Compile the lock files with gh-aw v0.91.1, the version pinned in them, so a
different local compiler cannot rewrite them. Never hand-edit a lock file.
gh extension install github/gh-aw --pin v0.91.1 --force
gh aw compile agentic-price-check agentic-model-price-check --no-check-updateThe agentic workflow opens at most one PR of verified price updates per run.
Verify every runtime
Add focused Python, JavaScript and Go tests for:
- provider selection by explicit provider ID
- provider selection by API URL and model namespace when supported
- representative input, cached-input, and output price calculation
- every usage extractor flavor
- aliases and context-sensitive matching that could collide
Put the Go tests in packages/go/api_test.go, which runs against the bundled provider data. Test updater parsing,
metadata preservation, write guards, and cassette replay in Python only: the updater lives in prices/src/prices/.
Run make build after every provider-data edit. This regenerates the v2 feed, package data, schemas, and provider inventory.
Never hand-edit those outputs or tests/dataset/usages.json.
Before handoff, run:
make all
git diff --checkInspect the provider YAML, cassette, and generated diff. Confirm that frozen v1 files are unchanged. Follow AGENTS.md for the
commit, PR description, AI disclaimer, CI monitoring, and review resolution.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

