setup-routing

setup-routing is a command for Claude Code from proticom/gnosys. It costs 0 tokens per session (390 once invoked), scanned A, original, MIT.

A wizard for choosing which language model and provider Gnosys uses for different kinds of tasks.

In plain words
What is it for?
Use it to configure routing for structuring, synthesis, vision, transcription, and Dream Mode tasks.
Why use it?
It lets you control task-specific model choices instead of using one default for every task.

Command for Claude Code

Written for Claude Code: a Claude Code command (commands/*.md).

Install

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.

agentmods
npx agentmods add commands/proticom/gnosys/setup-routing
Clone the repo
git clone --depth 1 https://github.com/proticom/gnosys

Made for: Claude Code.

Wrote 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.

agentmods badge for setup-routing

README.md
[![agentmods](https://agentmods.dev/badge/commands/proticom/gnosys/setup-routing.svg)](https://agentmods.dev/commands/proticom/gnosys/setup-routing)
Your own site
<a href="https://agentmods.dev/commands/proticom/gnosys/setup-routing"><img src="https://agentmods.dev/badge/commands/proticom/gnosys/setup-routing.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 390 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00390
Opus 5 $0.00000 $0.00195
Sonnet 5 $0.00000 $0.00078
Haiku 4.5 $0.00000 $0.00039

Measured 2d ago against content hash 87435cd353b0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

setup-routing 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 2d 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.

docs/commands/setup-routing.md · 47 lines

What it actually says

gnosys setup routing

Configure per-task LLM routing for Gnosys tasks.

Usage

gnosys setup routing

Behavior

  • Opens the interactive task-routing wizard.
  • Shows effective routing for structuring, synthesis, vision, transcription, and dream.
  • Lets you keep current routing, customize individual tasks, or reset task overrides to the default provider/model.
  • Updates Dream Mode routing when dream routing is enabled or changed.

Writes and side effects

  • Updates taskModels in the active Gnosys config.
  • Updates the dream config block when Dream Mode routing is changed.
  • Writes the resulting config under the active store, normally .gnosys/gnosys.json in the project or ~/.gnosys/gnosys.json globally.

Platform notes

macOS

  • Active store: Project .gnosys/gnosys.json when present; otherwise ~/.gnosys/gnosys.json.
  • API keys: Provider keys may be read from macOS Keychain, environment variables, or ~/.config/gnosys/.env when validating model choices.

Linux

  • Active store: Same project-first rule — .gnosys/gnosys.json in the current directory when the project is initialized.
  • API keys: GNOME Keyring (when available), environment variables, or ~/.config/gnosys/.env.

Windows

  • Active store: Project .gnosys/gnosys.json when initialized; otherwise the global config under the user profile.
  • API keys: Environment variables or ~/.config/gnosys/.env; set provider keys in PowerShell or System Environment Variables.

Validation

cd gnosys-public
npm run cli -- setup routing --help
Changes

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.

  1. 2d ago First seen · 47 lines · 0 tokens per session scan A 87435cd353b0

Subscribe to this mod's changes

setup-routing is a command published in the GitHub repository proticom/gnosys (4 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 390 tokens. 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-09-03.