pref-get

A command for reading saved user preferences, either one setting by key or all settings at once.

In plain words
What is it for?
Use it to inspect a preference such as coding style, list every saved preference, or get the result as JSON for another tool.
Why use it?
It lets you check the agent's stored instructions without opening the database or searching configuration files.

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/pref-get
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 450 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.00450
Opus 5 $0.00000 $0.00225
Sonnet 5 $0.00000 $0.00090
Haiku 4.5 $0.00000 $0.00045

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

Security

Grade A, and why

pref-get 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/pref-get.md · 97 lines

What it actually says

gnosys pref get

Get one user preference by key, or list all preferences.

Usage

gnosys pref get
gnosys pref get code-style
gnosys pref get --json
gnosys pref get code-style --json

Options

Option Description
--json Output as JSON

Behavior

  1. Opens the central DB via GnosysDB.openCentral().
  2. With a key: reads one preference via getPreference(centralDb, key).
  3. Without a key: lists all preferences via getAllPreferences(centralDb).

Output modes

Single preference (human):

Code Style (code-style)

Prefer small, focused changes

Confidence: high
Modified: 2026-05-28T...

List (human):

3 user preference(s):

  Code Style (code-style)
    Prefer small, focused changes

  ...

Single preference (JSON): preference object.

List (JSON): { "count": N, "preferences": [...] }

Empty list (JSON): { "preferences": [] }

Missing key:

No preference found for key "unknown-key".

Empty registry (human):

No preferences set. Use 'gnosys pref set <key> <value>' to add some.

Errors

Central DB unavailable:

Central DB not available (better-sqlite3 missing).

Other errors:

Error: <message>

Failure paths set process.exitCode = 1 and return through finally.

Validation

cd gnosys-public
npm run cli -- pref get --help
node scripts/audit-commands.mjs --write
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 · 97 lines · 0 tokens per session scan A d9ed58ca071f

Subscribe to this mod's changes

pref-get 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 450 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.