Borrowing it
Nothing to install: this file belongs to caidaoli/ccLoad. 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/caidaoli/ccLoad/master/.agents/skills/sync-cliproxy-core/SKILL.mdgit clone --depth 1 https://github.com/caidaoli/ccLoadWrote 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/caidaoli/ccload/sync-cliproxy-core)<a href="https://agentmods.dev/skills/caidaoli/ccload/sync-cliproxy-core"><img src="https://agentmods.dev/badge/skills/caidaoli/ccload/sync-cliproxy-core/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/caidaoli/ccload/sync-cliproxy-core"><img src="https://agentmods.dev/badge/skills/caidaoli/ccload/sync-cliproxy-core.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.02664 |
| Opus 5.5 | $0.00019 | $0.01066 |
| Sonnet 5.5 | $0.00009 | $0.00533 |
| Haiku 4.5 | $0.00005 | $0.00266 |
Grade A, and why
sync-cliproxy-core 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 25d 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
同步 CLIProxy 转换核心与渠道适配器
一次同步 CLIProxyAPI 的四协议纯转换核心、已登记 provider adapters 及其对应测试。保持 ccLoad Registry 和 provider wire 契约，不引入上游运行时系统。
- 默认调用
$sync-cliproxy-core时，自动固定上游最新稳定版本，并在同一次操作中完成 core 与全部已登记 provider adapters 的比较、集成、来源更新和验证；用户明确指定 commit/tag 时使用指定目标。 - 仅审计时保持只读：固定比较目标、核对来源与 manifest、报告差异和验证结果，不进入集成变更或更新来源步骤；未指定比较目标时使用
UPSTREAM.md已记录的 commit。 - 阅读或编辑本技能本身不执行同步。
原子同步契约
- core 与 provider adapters 必须来自同一 checkout 的同一不可变 commit；只生成一份变化清单，只更新一次来源 commit 和同步日期，只运行一套完成验证。
- 任一同步域无法移植、缺少匹配测试或验证失败时，整个同步未完成。不提供隐式 core-only 降级；用户明确缩小范围时只能审计，不得把部分写入报告成完整同步。
权威边界
- 按任务读取 协议转换边界、
internal/protocol/cliproxy/UPSTREAM.md、core snapshot manifest、provider adapter 语义边界和provider manifest。UPSTREAM.md是来源、固定提交和已落地状态的唯一事实源；core manifest 记录直接映射根、特殊映射、明确排除和最近一次 core/provider 原子差异的审查 blob，provider manifest 是 provider、逐文件映射、生产接线和契约测试的唯一 allowlist。 internal/protocol/registry.go定义四协议契约；internal/protocol/builtin/cliproxy_adapter.go处理通用输入验证、JSON/SSE 规范化和流帧封装；internal/protocol/cliproxy/providers/保存 provider-specific 纯转换。- provider 选择留在 ccLoad 请求上下文边界，按实际 wire dialect/AuthType 决定；不要把 provider 注册成第五种通用客户端协议。
- 不引入 CLIProxyAPI 的认证、配置、路由、缓存服务、插件、动态 Registry、executor 或网络刷新代码。Interactions 只有在 ccLoad 正式支持其线协议后才可登记。
- 不添加 CLIProxyAPI 运行时 Go module 依赖或
replace。源码继续使用ccLoad/internal/protocol/cliproxy/...导入路径。 - Registry 与 provider 边界测试是 ccLoad 兼容性权威。上游行为与本地线协议冲突时，修正根因并保留本地契约，不盲目覆盖。
同步流程
1. 预检
- 确认当前目录属于 ccLoad，并检查
git status --short。 - 保护已有修改。若工作区改动覆盖 core、providers、适配器、Registry、
go.mod、go.sum或UPSTREAM.md，先区分用户修改与本次同步；无法安全隔离时停止并说明冲突。 - 记录当前同步 commit 和目标 commit。
2. 固定目标
- 上游 checkout：本机存在
~/Source/go/CLIProxyAPI时优先使用，否则在临时目录克隆UPSTREAM.md记录的仓库。core、provider 生产源码与测试必须全部来自这个 checkout 的同一个 commit。 - 用户指定 commit/tag 时，解析成完整不可变 commit SHA。
- 用户未指定目标或只说“同步最新”时，以当前记录 tag 去掉
MAJOR.MINOR.PATCH后的前缀作为稳定 tag 系列（记录为fork/vX.Y.Z时系列为fork/v），按语义版本选最高版本并解引用为 commit；忽略预发布 tag，禁止按字典序或提交时间猜版本：
What ships with it
7 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.
- 25d ago Changed 90e34600b55d
- 1mo ago Changed · +13 lines 26703083551b
- 1mo ago Changed · -9 lines · -28 tokens per session 808dc1b5e24a
- 1mo ago First seen · 116 lines · 75 tokens per session scan A 004730896ad2
sync-cliproxy-core is a skill published in the GitHub repository caidaoli/ccLoad (428 stars, last pushed today), licensed MIT. It adds 47 tokens to every session and 2,664 once invoked, about $0.0002 per session on Opus 5.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
omni-inference
The core OpenAI-compatible inference endpoints: chat completions, embeddings, images, audio (TTS/STT), moderations, rerank, and the Responses API. The primary integration surface for AI agents.
omni-combos-routing
Create and manage routing combos with 19 strategies (priority, weighted, round-robin, Auto-combo, and more). Configure fallback chains, test routing outcomes, and retrieve combo metrics.
omni-providers
Manage provider connections, API keys, OAuth flows, and connection tests via the REST API. List, add, update, remove, and test AI provider integrations across OmniRoute's 375-provider catalog.
omni-api-keys
Create, list, rotate, and revoke OmniRoute API keys. Control per-key scopes, spending limits, and expiration. Keys gate access to all proxy and management endpoints.
omni-auth
Manage API key authentication and session tokens. Start here to authenticate requests via Bearer token, obtain session cookies, and configure login requirements for the OmniRoute API.
omni-mcp
Connect to the OmniRoute MCP server (110 tools, 3 transports: SSE/stdio/HTTP). Covers routing, cache, compression, memory, skills, providers, and audit tools across 33 permission scopes.