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-preferencesgit 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-preferences)<a href="https://agentmods.dev/commands/proticom/gnosys/setup-preferences"><img src="https://agentmods.dev/badge/commands/proticom/gnosys/setup-preferences.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 | $0.00000 | $0.00348 |
| Opus 5 | $0.00000 | $0.00174 |
| Sonnet 5 | $0.00000 | $0.00070 |
| Haiku 4.5 | $0.00000 | $0.00035 |
Grade A, and why
setup-preferences 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 yesterday.
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 preferences
Review and manage user-scope preferences used by Gnosys agents.
Usage
gnosys setup preferences
Behavior
- Opens the interactive preferences review screen.
- Lists active user-scope memories, including native preferences and imported/unknown user memories.
- Lets you create a new preference.
- Lets you view, edit, keep, or delete existing preferences.
- Returns to setup after you back out.
Writes and side effects
- Reads active user-scope memories from the central Gnosys DB.
- Creates or updates
pref-<key>preference memories throughsetPreference. - Deletes preference memories through
deletePreference, with direct delete fallback for legacy IDs. - Preference values are later injected into agent rules/system prompt context.
Platform notes
macOS
- Storage: User-scope preferences live in the central Gnosys DB (
~/.gnosys/gnosys.dbby default). - Access: Same DB path whether invoked from Terminal, iTerm, or IDE-integrated terminals.
Linux
- Storage: Same central DB under
~/.gnosys/gnosys.db(or the configured remote store when sync is enabled). - Access: Works from any shell session with read/write access to the Gnosys home directory.
Windows
- Storage: Central DB under the user profile (
~/.gnosys/gnosys.db). - Access: Run from PowerShell or cmd; ensure the Gnosys home directory is writable.
Validation
cd gnosys-public
npm run cli -- setup preferences --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.
- yesterday First seen · 49 lines · 0 tokens per session scan A 52984aeb9f8e
setup-preferences is a command published in the GitHub repository proticom/gnosys (4 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 348 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
wrap
Close the session cleanly. Update entity state. Capture decisions. Detect momentum shifts.
start
"What accumulated? What's blocking? Where do I begin?".
promote
Move .memory/ artifacts to permanent knowledge locations.
checkpoint
Create or update .memory/ with current conversation state.
cleanup
Delete promoted content from the .memory/ directory.
gains
Show what Kage saved you — tokens, cost, stale memories blocked, stale knowledge caught.