config-set

A command for changing settings in the active writable Gnosys store, such as the language-model provider, model, server URL, or search preferences.

In plain words
What is it for?
Use it to select providers and models, set local or custom service endpoints, save API keys, and adjust memory recall settings.
Why use it?
It keeps configuration in one place so commands use the intended provider, model, and memory-search behavior.

Command

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/config-set
Clone the repo
git clone --depth 1 https://github.com/proticom/gnosys
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 857 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 $0.00000 $0.00857
Opus 5 $0.00000 $0.00428
Sonnet 5 $0.00000 $0.00171
Haiku 4.5 $0.00000 $0.00086

Measured 2d ago against content hash 9e4bc9ee94d5, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

config-set 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/config-set.md · 87 lines

How it starts

The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.

gnosys config set

Set a config value in the active writable Gnosys store.

Usage

gnosys config set provider openai
gnosys config set model gpt-4.1
gnosys config set ollama-url http://127.0.0.1:11434
gnosys config set openai-model gpt-4.1
gnosys config set openai-url https://api.openai.com/v1
gnosys config set task structuring openai gpt-4.1-mini
gnosys config set task synthesis anthropic claude-sonnet-4-20250514
gnosys config set recall aggressive false
gnosys config set recall maxMemories 8
gnosys config set recall minRelevance 0.35
gnosys config set custom-key sk-...

Supported keys

Key Value Notes
provider provider name Sets default LLM provider
model model id Updates model for the current default provider
ollama-url, ollama-model url / model Ollama endpoint and model
anthropic-model, groq-model, openai-model, openai-url model or url Provider-specific overrides
lmstudio-url, lmstudio-model url / model LM Studio settings
xai-model, mistral-model model id xAI and Mistral models
custom-url, custom-model, custom-key url / model / key Custom OpenAI-compatible provider
task structuring|synthesis + provider + model Three extra args required
recall sub-field + value See recall sub-fields below

Recall sub-fields: aggressive (true/false), maxMemories (integer), minRelevance (0–1 float).

Behavior

  • Validates the top-level key against a known set before writing; unknown keys exit with a did you mean \...`?` hint when close.
  • Resolves the active writable store; exits with no writable store found when none is available.
  • Updates gnosys.json atomically via writeConfig.
  • Prints a header, before/after diff (when applicable), and a saved confirmation with store source (project vs global).
  • Sensitive values are not echoed in diff output; custom-key marks the value as (set).
  • Invalid provider, task name, or recall value exits with a specific error message.

Read the full file on GitHub · 87 lines

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 · 87 lines · 0 tokens per session scan A 9e4bc9ee94d5

Subscribe to this mod's changes

config-set is a command published in the GitHub repository proticom/gnosys (4 stars, last pushed 16d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 857 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-08-31.