Borrowing it
Nothing to install: this file belongs to nawodyaishan/universal-mcp-sync. 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/nawodyaishan/universal-mcp-sync/main/.claude/skills/add-provider/SKILL.mdgit clone --depth 1 https://github.com/nawodyaishan/universal-mcp-syncWrote 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/nawodyaishan/universal-mcp-sync/add-provider)<a href="https://agentmods.dev/skills/nawodyaishan/universal-mcp-sync/add-provider"><img src="https://agentmods.dev/badge/skills/nawodyaishan/universal-mcp-sync/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/nawodyaishan/universal-mcp-sync/add-provider"><img src="https://agentmods.dev/badge/skills/nawodyaishan/universal-mcp-sync/add-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.00070 | $0.00656 |
| Opus 5 | $0.00035 | $0.00328 |
| Sonnet 5 | $0.00014 | $0.00131 |
| Haiku 4.5 | $0.00007 | $0.00066 |
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 11d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add Provider Procedure
We follow a strict Spec-Driven Development (SDD) workflow. When requested to add a new MCP provider to usync, strictly follow these steps:
0. SDD Pre-requisite
Ensure an approved specification document exists (e.g., docs/specs/add-<name>-provider.md). If it doesn't exist or hasn't been approved, use the agentic-sdd-router or agentic-sdd-spec skill to create and refine the spec first. Do not proceed to implementation without a spec.
1. STOP and gather
Read the following files to understand the system context:
pkg/provider/types.gopkg/provider/exa.gopkg/provider/context7.godocs/contributors/adding-a-provider.mddocs/specs/providers/add-context7-provider.md
2. Look up official docs
Use your search tools (or the Context7 MCP if available) to query the target server's configuration schema. Identify if it requires an API key, env vars, or specific arguments.
3. Decide capabilities
Use the decision tree from adding-a-provider.md:
- Is it
stdioor a remote transport? - Does it use URL query auth or Header auth?
- Is it a single-key or multi-key setup?
4. Scaffold helpers
If necessary, create a package at pkg/<id>/ for validation logic (e.g., keys.go, keys_test.go).
Reference: references/code-templates.md (Template 1).
5. Implement provider
Create pkg/provider/<id>.go implementing the MCPProvider interface.
Reference: references/code-templates.md (Template 2).
6. Register
Register your new provider in DefaultRegistry() inside pkg/provider/registry.go.
7. Per-client adaptation
If the provider uses headers, verify if any client-specific adaptations are needed in pkg/client/adapter.go (e.g., HeadersFor).
8. QA scenarios
Write end-to-end scenarios in pkg/app/qa_scenarios_test.go confirming the config gets emitted accurately.
Reference: references/code-templates.md (Template 3).
9. Docs
Add a row to the Provider Matrix in README.md.
Update docs/contributors/adding-a-provider.md if the architectural approach expands.
What ships with it
3 files 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.
- 11d ago First seen · 60 lines · 70 tokens per session scan A 12aa189503bf
add-provider is a skill published in the GitHub repository nawodyaishan/universal-mcp-sync (6 stars, last pushed 1mo ago), licensed MIT. It adds 70 tokens to every session and 656 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
agent-manager
Run a fleet of AI coding agents as live tmux sessions with agent-manager. Use when a developer is running more than one coding agent, needs to see which one is working or blocked, wants to spawn another on an independent task, or wants to review an agent's diff without leaving the terminal.
agent-manager-reference
Query agent-manager.dev's reference API and MCP server for documentation, the coding CLIs it manages, the tools its MCP server exposes, and the current release. Use instead of scraping the website's HTML.
tui-design
Design, build, refactor, or review terminal interfaces—full-screen TUIs, interactive prompts, and command-line tools. Use for terminal-app layout and UX, CLI behavior, ncurses-style tools, dashboards, REPLs, fzf-like pickers, and libraries such as Bubble Tea, Ratatui, Textual, or Ink, including requests that name a…
subagent-driven-development
Orchestrating sub-agents through TDD phases for complex features.
systematic-debugging
4-phase debugging protocol for diagnosing and fixing failing tests.
test-driven-development
Red-green-refactor TDD implementation cycle.