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 agentmods add commands/proticom/gnosys/setup-routinggit clone --depth 1 https://github.com/proticom/gnosysWrote 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/commands/proticom/gnosys/setup-routing)<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>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.00000 | $0.00390 |
| Opus 5 | $0.00000 | $0.00195 |
| Sonnet 5 | $0.00000 | $0.00078 |
| Haiku 4.5 | $0.00000 | $0.00039 |
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.
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
taskModelsin the active Gnosys config. - Updates the
dreamconfig block when Dream Mode routing is changed. - Writes the resulting config under the active store, normally
.gnosys/gnosys.jsonin the project or~/.gnosys/gnosys.jsonglobally.
Platform notes
macOS
- Active store: Project
.gnosys/gnosys.jsonwhen present; otherwise~/.gnosys/gnosys.json. - API keys: Provider keys may be read from macOS Keychain, environment variables, or
~/.config/gnosys/.envwhen validating model choices.
Linux
- Active store: Same project-first rule —
.gnosys/gnosys.jsonin 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.jsonwhen 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
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.
- 2d ago First seen · 47 lines · 0 tokens per session scan A 87435cd353b0
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.
Other commands, from other repositories
stripe-backend
Centralized LLM prompt instructions for Copilot and Cursor, including scripts to convert and sync rules for Python, React, Shell, and TypeScript. Designed for rapid reuse and contribution across projects.
langchain-agent
You are an expert LangChain agent developer specializing in production-grade AI systems using LangChain 0.1+ and LangGraph.
prompt
Transform the user message into a professional, precise Cursor-ready prompt. Never execute the requested task. Output only the optimized prompt package.
generate-prompts
Apply .agents/tasks/prompt-generation.md.
prompt-eval-debug
Debug any prompt with a tiny eval suite (control, edge, boundary), failure diagnosis, and smallest next change, no blind rewrite.
prompt-pilot
Rewrite a rough prompt into a precise, context-enriched prompt (read-only — never implements the task).