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/prefgit clone --depth 1 https://github.com/proticom/gnosysWhat 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.00563 |
| Opus 5 | $0.00000 | $0.00282 |
| Sonnet 5 | $0.00000 | $0.00113 |
| Haiku 4.5 | $0.00000 | $0.00056 |
Grade A, and why
pref 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gnosys pref
Manage user-scoped preferences stored as memories and surfaced into agent context.
Usage
gnosys pref set code-style "Prefer small, focused changes"
gnosys pref set code-style "Prefer small changes" --title "Code Style" --tags coding,workflow
gnosys pref get
gnosys pref get code-style
gnosys pref get --json
gnosys pref delete code-style
Subcommands
pref set <key> <value>
Set a user preference. Keys should be kebab-case.
| Option | Description |
|---|---|
-t, --title <title> |
Human-readable title |
--tags <tags> |
Comma-separated tags |
Validates against known preference keys and suggests corrections via suggestPreferenceKey when a close match exists.
After setting, run gnosys sync to update agent rules files.
pref get [key]
Get one preference by key, or list all preferences when no key is given.
| Option | Description |
|---|---|
--json |
Output as JSON |
pref delete <key>
Delete a user preference by key. Run gnosys sync afterward to refresh agent rules files.
Behavior
- Opens the central DB via
GnosysDB.openCentral(). - Uses
setPreference,getPreference,getAllPreferences, anddeletePreferencefromsrc/lib/preferences.js. - Preferences are user-scoped memories, not project-scoped.
- Review and clean up preferences with
gnosys setup preferences.
Output
Set success:
Preference set: Code Style
Key: code-style
Value: Prefer small changes
Run 'gnosys sync' to update agent rules files.
Get JSON (--json): single preference object or { count, preferences } for list mode.
Errors
Central DB unavailable:
Central DB not available (better-sqlite3 missing).
Unknown key with suggestion:
Unknown preference key `code-styl` — did you mean `code-style`?
Other errors:
Error: <message>
Failure paths set process.exitCode = 1 and return through finally.
Validation
cd gnosys-public
npm run cli -- pref --help
npx vitest run src/test/pref-command-handler.test.ts
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 · 98 lines · 0 tokens per session scan A 5f61cde3720c
pref 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 563 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.
Other commands, from other repositories
init-project
Configure this project for Obsidian PKM — connects the repo to a vault project folder and writes CLAUDE.md integration directives.
setup
Configure Vault PKM plugin — set vault path, API keys, and verify setup.
setup-pm-skills
Onboard a new user — find out what they do, recommend the right bundles & top skills, and set up a project CONTEXT.md so every skill is tailored to them.
statusbar-style
Switch the status-bar style (classic / capsule / hairline).
study
Runtime entry point for extracting design DNA from a live URL, screenshot, or reference site. Part of the Discovery lifecycle phase.
competitive-landscape
Map the competitive landscape for a market or company.