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-modelsgit 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-models)<a href="https://agentmods.dev/commands/proticom/gnosys/setup-models"><img src="https://agentmods.dev/badge/commands/proticom/gnosys/setup-models.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.00597 |
| Opus 5 | $0.00000 | $0.00298 |
| Sonnet 5 | $0.00000 | $0.00119 |
| Haiku 4.5 | $0.00000 | $0.00060 |
Grade A, and why
setup-models 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.
How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gnosys setup models
Update the default LLM provider and model, optionally validate provider connectivity with a test API call.
Usage
gnosys setup models
gnosys setup models --provider xai --model grok-4.20
gnosys setup models --provider ollama --model llama3.2 --no-validate
gnosys setup models -p anthropic -m claude-sonnet-4-20250514
Options
-p, --provider <name>— Set provider directly:anthropic,openai,xai,groq,mistral,openrouter,ollama,lmstudio, orcustom.-m, --model <name>— Set model name for the chosen provider.--no-validate— Skip the test API call after configuration.
Behavior
- Runs the interactive models setup flow when no flags are passed.
- With
--providerand/or--model, applies configuration non-interactively. - By default, validates the provider with a test API call unless
--no-validateis set. - Writes provider and model settings to the active Gnosys config (
~/.gnosys/gnosys.json).
Writes and side effects
- Updates LLM provider and model in config.
- May store or read provider API keys from the platform secure store or
~/.config/gnosys/.env. - OpenRouter: provider
openroutercallshttps://openrouter.ai/api/v1with your OpenRouter API key. The setup wizard lists:freemodels (e.g.nvidia/nemotron-3-super-120b-a12b:free) plus paid tiers from the live catalog. - May print shell-profile or env-file hints when keys are missing.
Platform notes
macOS
- API keys: macOS Keychain (recommended), environment variables, or
~/.config/gnosys/.env - Shell profile:
~/.zshrcor~/.bash_profilefor manualexport ANTHROPIC_API_KEY=...(provider-specific)
Linux
- API keys: GNOME Keyring when
secret-toolis available, environment variables, or~/.config/gnosys/.env - Shell profile:
~/.bashrcor~/.zshrcfor manual env vars
Windows
- API keys: Environment variables or
~/.config/gnosys/.env - Shell profile: PowerShell profile (
$PROFILE) or System Properties → Environment Variables
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 · 57 lines · 0 tokens per session scan A 75c51c2e8582
setup-models 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 597 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).