A command-line tool for viewing and changing the language-model settings used by an active Gnosys store.

Use it to inspect settings, choose a provider or model, configure provider URLs, adjust task routing or recall options, and create a configuration file.

It puts provider, model, task-routing, and recall settings in one place and shows where changes are saved.

config — Command by proticom

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

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

Model	Per session	Once invoked
Fable 5	$0.00000	$0.00510
Opus 5	$0.00000	$0.00255
Sonnet 5	$0.00000	$0.00102
Haiku 4.5	$0.00000	$0.00051

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

Security

Grade A, and why

config 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.md · 50 lines

What it actually says

gnosys config

View and manage LLM provider configuration for the active Gnosys store.

Usage

gnosys config show
gnosys config show --json
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 task structuring openai gpt-4.1-mini
gnosys config set recall maxMemories 8
gnosys config init
gnosys config init --force

Behavior

show reads config from the first active store and prints a human-readable SOC summary (default provider, per-provider models/keys, task routing). With --json, dumps the effective config object as JSON for scripts.
set <key> <value> [extra...] validates the key, updates the writable store's gnosys.json, prints a diff, and labels whether the write landed in project or global scope. Supported keys include provider, model, provider-specific URLs/models, task, and recall sub-fields.
init without --force is deprecated: prints a warning and points users to gnosys setup. With --force, writes a blank gnosys.json template to the writable store if one does not already exist.

Platform notes

macOS

Config file lives at <store-path>/gnosys.json (project: ./.gnosys/gnosys.json, personal: ~/.gnosys/gnosys.json).
API keys may come from the config file or environment variables (ANTHROPIC_API_KEY, OPENAI_API_KEY, etc.).

Linux

Same layout as macOS. Use quoted paths when pointing GNOSYS_PERSONAL at a custom store.

Windows

Store paths use backslashes in output; Node resolves them correctly.
Environment variables for API keys work the same as on Unix (set OPENAI_API_KEY=... in cmd, $env:OPENAI_API_KEY="..." in PowerShell).

Validation

cd gnosys-public
npm run cli -- config --help
npm run cli -- config show --help
npm run cli -- config set --help
npm run cli -- config init --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.

2d ago First seen · 50 lines · 0 tokens per session scan A 2fd9605484ae

Subscribe to this mod's changes

config 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 510 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.

Data and AI LLM Memory and context Writing and docs ai ai-agents ai-tools developer-tools knowledge-management

config

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

gnosys config

Usage

Behavior

Platform notes

macOS

Linux

Windows

Validation

What this file has done since we first saw it

Other commands, from other repositories

init-project

setup

setup-pm-skills

statusbar-style

study

competitive-landscape