Borrowing it
Nothing to install: this file belongs to ProfSynapse/nexus. 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/ProfSynapse/nexus/main/.claude/skills/nexus-llm-adapters/SKILL.mdgit clone --depth 1 https://github.com/ProfSynapse/nexusWrote 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/profsynapse/nexus/nexus-llm-adapters)<a href="https://agentmods.dev/skills/profsynapse/nexus/nexus-llm-adapters"><img src="https://agentmods.dev/badge/skills/profsynapse/nexus/nexus-llm-adapters.svg" alt="Measured on agentmods" 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.00075 | $0.00677 |
| Opus 5 | $0.00037 | $0.00338 |
| Sonnet 5 | $0.00015 | $0.00135 |
| Haiku 4.5 | $0.00007 | $0.00068 |
Grade A, and why
nexus-llm-adapters 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 7d 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nexus LLM adapters
Adapters live in src/services/llm/adapters/{provider}/ and extend BaseAdapter,
which talks direct HTTP through ProviderHttpClient. There are no vendor LLM SDKs
in this repo; adding one is a decision to raise, not to make.
This router points at the procedure. The detail loads when you take the path.
Workflow
- Adding or changing an adapter — follow
protocols/add-adapter.md. It is a wiring checklist; work it in order rather than pattern-matching an existing adapter, because the pieces that get forgotten are the ones no compiler checks. - Chat is blank, missing reasoning, looping, or doubling — follow
protocols/debug-adapter.md. Start from the symptom, not the adapter source: these failures have known causes and reading code first wastes the trip. - Before calling any adapter change done — run
protocols/verify-adapter.md. You MUST exercise the non-streaming path, the streaming path, and the streaming error path separately; they fail independently and unit tests prove none of them. You MUST also runscripts/check_stream_error_wiring.pyon the adapter you touched and get a zero exit. - End of a session that used this skill — run
protocols/self-refine.md.
Map
protocols/the procedures: add-adapter, debug-adapter, verify-adapter, self-refine.references/mechanism and rationale, read on demand:symptoms.md(the symptom→cause lookup the debug protocol enters through),streaming-contract.md,reasoning-rendering.md,local-providers.md,cli-providers.md,chat-plumbing.md.scripts/check_stream_error_wiring.py— checks that an adapter parsing an SSE stream wiresextractError. Run it, do not re-derive it by reading source.
Siblings — do not duplicate them here
nexus-model-updatesowns model metadata: ids, pricing, context windows, capability flags, provider defaults, and the live provider smoke test.nexus-model-evalandnexus-eval-harnessown grading models on tool use.nexus-testingowns test lanes, what a mock can prove, and the in-app loop.nexus-mobile-compatowns Node imports, dependency vetting, and desktop-only gating — which every adapter that shells out or touches the filesystem needs.
What ships with it
12 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.
- protocols/add-adapter.md 4.5 KB
- protocols/debug-adapter.md 2.8 KB
- protocols/self-refine.md 2.0 KB
- protocols/verify-adapter.md 3.5 KB
- references/chat-plumbing.md 2.3 KB
- references/cli-providers.md 3.4 KB
- references/local-providers.md 4.4 KB
- references/reasoning-rendering.md 4.1 KB
- references/streaming-contract.md 5.4 KB
- references/symptoms.md 5.4 KB
- refinement-log.md 4.7 KB
- scripts/check_stream_error_wiring.py 7.0 KB runs code
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.
- 7d ago First seen · 50 lines · 75 tokens per session scan A cb1929bf6dcf
nexus-llm-adapters is a skill published in the GitHub repository ProfSynapse/nexus (154 stars, last pushed 4d ago), licensed MIT. It adds 75 tokens to every session and 677 once invoked, about $0.0004 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
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.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
agui-dotnet-protobuf
Use the protobuf wire transport (instead of the default Server-Sent Events) for an AG-UI connection with the AG-UI .NET SDK — a compact binary event stream negotiated via the Accept header. USE FOR: making an AGUIChatClient prefer protobuf by wiring an AGUIEventStreamHandler with ProtobufEventStreamFormatter (then…
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
fastapi-router-py
Create FastAPI routers with CRUD operations, authentication dependencies, and proper response models. Use when building REST API endpoints, creating new routes, implementing CRUD operations, or adding authenticated endpoints in FastAPI applications.
telnyx-messaging-hosted-curl
Set up hosted SMS numbers, toll-free verification, and RCS messaging. Use when migrating numbers or enabling rich messaging features. This skill provides REST API (curl) examples.