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 skills add cyanheads/mcp-ts-core --skill add-providergit clone --depth 1 https://github.com/cyanheads/mcp-ts-coreWrote 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/cyanheads/mcp-ts-core/add-provider)<a href="https://agentmods.dev/skills/cyanheads/mcp-ts-core/add-provider"><img src="https://agentmods.dev/badge/skills/cyanheads/mcp-ts-core/add-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/cyanheads/mcp-ts-core/add-provider"><img src="https://agentmods.dev/badge/skills/cyanheads/mcp-ts-core/add-provider.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00047 | $0.01667 |
| Opus 5 | $0.00023 | $0.00834 |
| Sonnet 5 | $0.00009 | $0.00333 |
| Haiku 4.5 | $0.00005 | $0.00167 |
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 today.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- add-provider — 100% identical, 22 lines differ
How it starts
The opening of the file, as written. The whole thing — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context
Providers implement interfaces defined in core. They are selected at runtime via config
(e.g., STORAGE_PROVIDER_TYPE). Tier 3 providers lazy-load their dependencies to keep the
core bundle small.
Providers live inside the package source tree — import the interface via relative path
(e.g., import type { IStorageProvider } from '../core/IStorageProvider.js'), not via the
package subpath exports (those are for consumers).
Provider interfaces
| Domain | Interface file |
|---|---|
| Storage | src/storage/core/IStorageProvider.ts |
| LLM | src/services/llm/core/ILlmProvider.ts |
| Speech | src/services/speech/core/ISpeechProvider.ts |
Read the relevant interface fully before implementing — each has distinct required members.
ISpeechProvider in particular requires readonly name, readonly supportsTTS,
readonly supportsSTT, and healthCheck() in addition to the capability methods;
these flags drive routing in SpeechService.
File conventions
Provider file location and naming differ by domain:
-
Storage — nested subdirectory, camelCase directory name, PascalCase-suffixed provider file. Each provider gets its own subdirectory for the provider file plus any co-located types:
src/storage/providers/{{providerName}}/{{providerName}}Provider.ts(e.g.,src/storage/providers/inMemory/inMemoryProvider.ts,src/storage/providers/supabase/supabaseProvider.ts+supabase.types.ts) -
LLM / Speech — flat directory, kebab-case with
.provider.tssuffix:src/services/llm/providers/{{provider-name}}.provider.tssrc/services/speech/providers/{{provider-name}}.provider.ts(e.g.,src/services/llm/providers/openrouter.provider.ts,src/services/speech/providers/elevenlabs.provider.ts)
Steps
- Identify the provider interface — read the interface file for the target domain (see table above).
- Create the provider file following the file convention for its domain (see above).
- Implement the interface — all methods must be implemented. Storage providers build
on
src/storage/core/providerHelpers.tsrather than re-deriving what the existing providers share:
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.
- today Changed · +14 lines 0996adf1c312
- 10d ago First seen · 124 lines · 47 tokens per session scan A f96194818689
add-provider is a skill published in the GitHub repository cyanheads/mcp-ts-core (151 stars, last pushed yesterday), licensed Apache-2.0. It adds 47 tokens to every session and 1,667 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-30.
Other skills, from other repositories
openclaw-json-toolkit
Enterprise-grade JSON processing suite — format, validate, deep-diff, JSONPath query, structural transform, and schema generation in one MCP server. Use when: (1) user says 'format this JSON' or 'pretty print this', (2) user asks 'validate my JSON' or 'is this valid JSON', (3) user needs to 'compare two JSON objects'…
frontmcp-observability
Use when adding tracing, structured logging, metrics, or monitoring to a FrontMCP server. Covers zero-config OpenTelemetry distributed tracing across all flows; the this.telemetry API for custom spans, events, and attributes in tools, plugins, agents, and skills; structured JSON logging with trace correlation and…
blazemeter-api-monitoring
Comprehensive guide for BlazeMeter API Monitoring, including test creation, configuration, scripting, integrations, notifications, and management. Use when working with API Monitoring tests for (1) Creating and configuring API tests, (2) Writing custom scripts (Initial, Pre-request, Post-response), (3) Integrating…
diagnose-connectivity
Work out why a 3x-ui client cannot connect, in the order that finds the cause fastest — scope the outage, check the core, the inbound, the client's own limits, routing and outbounds, then the node. Use whenever someone reports "it stopped working", a client cannot connect, a site is unreachable through the proxy, or…
aurora-backend-setup
Set up, build, or troubleshoot the AURORA Agent (bioprism) MCP server used by the aurora-backend plugin. Use when the aurora-agent MCP server fails to start, when its tools are missing from a session, when asked to install or build the aurora-agent backend, or when a bioprism build or test behaves strangely on Windows.
spotify-exhaustive-feature-sweep
Exhaustive feature sweep across Spotify domains — enumerate all endpoints into quantity-first tool proposals with quota flags and batched GitHub logging.