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 techysy/10router --skill 10router-add-providergit clone --depth 1 https://github.com/techysy/10routerWrote 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/techysy/10router/10router-add-provider)<a href="https://agentmods.dev/skills/techysy/10router/10router-add-provider"><img src="https://agentmods.dev/badge/skills/techysy/10router/10router-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/techysy/10router/10router-add-provider"><img src="https://agentmods.dev/badge/skills/techysy/10router/10router-add-provider.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 5 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Supply Chain · line 65 Remote code is downloaded and executed. This bypasses code review and could introduce malicious code.Fix: Avoid downloading and executing remote scripts. Use trusted packages from PyPI/npm. If remote fetch is required, verify checksums and use HTTPS.
- medium Data Exfiltration · line 47 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 53 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 65 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 115 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00087 | $0.01661 |
| Opus 5 | $0.00044 | $0.00830 |
| Sonnet 5 | $0.00017 | $0.00332 |
| Haiku 4.5 | $0.00009 | $0.00166 |
Grade A, and why
10router-add-provider scanned grade A with 1 finding 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 6d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -X POST $TENROUTER_URL/api/provider-nodes \ How it starts
The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
10Router — Add a Custom Provider (Self-Serve)
Lets an AI agent (or user) call the internal management API of a running 10Router to
register a custom OpenAI/Anthropic-compatible upstream (baseUrl + its own key + models) as a
routable node. No source change / no repackage, no restart needed — live for subsequent /v1/* requests immediately.
Requires TENROUTER_URL (and an admin-capable auth key). Entry skill:
https://raw.githubusercontent.com/techysy/10router/main/skills/10router/SKILL.md
Confirm three things first
| Item | Notes |
|---|---|
| Target URL | $TENROUTER_URL (management API port follows your deployment; NAS/fnOS often :20127, adjust per instance) |
| Auth | dashboard LLM key (below) or the deployer's own CLI token |
| Model routing | custom-node models MUST be {prefix}/{model} — never a bare model name |
Auth: dashboard LLM key (the self-serve exemption)
Only POST /api/provider-nodes and POST /api/providers at the root path are open to a
dashboard LLM API key (a key from Dashboard → Keys). GET/PUT/DELETE and [id] sub-routes still
need the deployer's CLI token / login JWT.
AUTH="Authorization: Bearer ${TENROUTER_KEY}" # TENROUTER_KEY = dashboard LLM key
Deployers can also derive a CLI token on the host from
machine-id+cli-secret:sha256(machine-id + "9r-cli-auth" + cli-secret).slice(0,16), fixed salt9r-cli-auth. Custom data paths live under your DATA_DIR (~/.10router/or fnOS/vol4/@appdata/10router/).
Two-step registration
10Router splits a "custom-compatible node" into two steps: first create a node (baseUrl/prefix/type), then a connection (its upstream key, linked to the node).
Step 1: create an openai-compatible node
curl -s -X POST $TENROUTER_URL/api/provider-nodes \
-H "Content-Type: application/json" -H "$AUTH" \
-d '{
"name": "JustWorker",
"prefix": "justworker",
"apiType": "chat",
"baseUrl": "https://api.justwoker.icu/v1",
"type": "openai-compatible"
}'
# → {"node":{"id":"openai-compatible-chat-<uuid>","prefix":"justworker",...}}
What ships with it
1 file 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.
- 6d ago First seen · 135 lines · 87 tokens per session scan A aedc01c0e0a9
10router-add-provider is a skill published in the GitHub repository techysy/10router (25 stars, last pushed today), licensed MIT. It adds 87 tokens to every session and 1,661 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-04.
Other skills, from other repositories
keirouter
Entry point for KeiRouter — local/remote AI gateway with OpenAI-compatible REST for chat, image, TTS, embeddings, web search, web fetch. Use when the user mentions KeiRouter, KEIROUTERURL, or wants AI without writing provider boilerplate. This skill covers setup + indexes capability skills; fetch the relevant…
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-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 327-provider catalog.
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-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-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.