Borrowing it
Nothing to install: this file belongs to AlexisBalayre/claude-code-power-config. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/AlexisBalayre/claude-code-power-config/main/.claude/skills/new-provider/SKILL.mdgit clone --depth 1 https://github.com/AlexisBalayre/claude-code-power-configWrote 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/alexisbalayre/claude-code-power-config/new-provider)<a href="https://agentmods.dev/skills/alexisbalayre/claude-code-power-config/new-provider"><img src="https://agentmods.dev/badge/skills/alexisbalayre/claude-code-power-config/new-provider/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/alexisbalayre/claude-code-power-config/new-provider"><img src="https://agentmods.dev/badge/skills/alexisbalayre/claude-code-power-config/new-provider.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00060 | $0.00500 |
| Opus 5 | $0.00030 | $0.00250 |
| Sonnet 5 | $0.00012 | $0.00100 |
| Haiku 4.5 | $0.00006 | $0.00050 |
Grade A, and why
new-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 10d 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.
What it actually says
Scaffold a new delivery Provider. The adapter/factory/registry obligations are in docs/conventions/services.md §Delivery Providers - read it first; this skill is the execution checklist.
Execution Steps
- Determine Channel & Context: Which Channel -
email,sms,push, orwebhook? Read 2-3 existing examples inpackages/acme-providers/src/providers/clients/andsrc/interfaces/before writing code. - Adapter -
src/providers/clients/<channel>/<provider>/<provider>-<channel>.adapter.ts:- Implement the Channel interface (
EmailProvider,SmsProvider,PushProvider, orWebhookProviderfromsrc/interfaces/). - Use shared SDK clients (
src/providers/clients/sdk/<system>.client.ts) if applicable. Handle retries and partial failures explicitly. - Add JSDoc to every exported method (packages require it).
- Implement the Channel interface (
- Factory -
src/providers/factories/<channel>.factory.ts:- Add the new provider ID literal to the union type in
src/interfaces/<channel>.interface.tsso the factory switch fails to compile until the new case is handled. - Add the new case to the factory switch (
createProvider(channel, id, deps)).
- Add the new provider ID literal to the union type in
- Config -
config/<channel>/<provider>.yaml:- Define endpoints, options, and rate limits. NEVER hardcode credentials - read them via env.
- Update Exports: Ensure correct exposure via subpath exports in
src/index.ts. - Tests -
test/unit/providers/clients/<channel>/<provider>/<provider>-<channel>.test.ts:- Mock the external SDK. ALWAYS mock
@acme/acme-logger. - Test success, error handling, retry/backoff, and config mapping.
- Mock the external SDK. ALWAYS mock
- Verify:
pnpm --filter @acme/acme-providers typecheckpnpm --filter @acme/acme-providers test
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.
- 10d ago First seen · 28 lines · 60 tokens per session scan A 4472c27d263a
new-provider is a skill published in the GitHub repository AlexisBalayre/claude-code-power-config (2 stars, last pushed 1mo ago), licensed MIT. It adds 60 tokens to every session and 500 once invoked, about $0.0003 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
kafka-event-driven-design
Kafka event-driven architecture designer and reviewer, at the application/client layer. ALWAYS use when designing, reviewing, or troubleshooting how a service produces or consumes Kafka events — topic and partition-key design, producer and consumer client configuration, consumer group topology, event schema definition…
api-design
REST API contract designer and reviewer. ALWAYS use when designing new endpoints, reviewing existing API contracts, planning API versioning, or standardizing error models. Covers resource modeling (URL/naming), HTTP method semantics, status code selection, error model consistency, pagination/filtering/sorting…
thirdparty-api-integration-test
Create and run gated Go integration tests for third-party APIs with real external calls, strict configuration gates, bounded timeouts, and safe runtime controls. Use for vendor/client contract verification and failure triage.
django-patterns
Django architecture patterns, REST API design with DRF, ORM best practices, caching, signals, middleware, and production-grade Django apps.
backend-patterns
Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes. Use when building or reviewing Node.js, Express, or Next.js API routes and their data access.
fastapi-patterns
FastAPI patterns for async APIs, dependency injection, Pydantic request and response models, OpenAPI docs, tests, security, and production readiness.