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/pref-setgit 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.00455 |
| Opus 5 | $0.00000 | $0.00228 |
| Sonnet 5 | $0.00000 | $0.00091 |
| Haiku 4.5 | $0.00000 | $0.00046 |
Grade A, and why
pref-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.
What it actually says
gnosys pref set
Set a user-scoped preference memory.
Usage
gnosys pref set <key> <value>
gnosys pref set code-style "Prefer small, focused changes"
gnosys pref set code-style "Prefer small changes" --title "Code Style"
gnosys pref set code-style "Prefer small changes" --tags coding,workflow
Options
| Option | Description |
|---|---|
-t, --title <title> |
Human-readable title for the preference |
--tags <tags> |
Comma-separated tags |
Behavior
- Opens the central DB via
GnosysDB.openCentral(). - Validates the key against known preference keys; suggests a close match via
suggestPreferenceKeywhen applicable. - Stores the preference with
setPreference(centralDb, key, value, { title, tags }). - Prints confirmation and reminds you to run
gnosys syncto update agent rules files.
Preferences are user-scoped memories surfaced into every agent's context, not project-scoped.
Output
Preference set: Code Style
Key: code-style
Value: Prefer small changes
Run 'gnosys sync' to update agent rules files.
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 set --help
node scripts/audit-commands.mjs --write
Related commands
- gnosys pref — parent command overview
- gnosys pref get — read preferences
- gnosys pref delete — remove a preference
gnosys sync— regenerate agent rules from preferences
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 · 76 lines · 0 tokens per session scan A e4f25bc53042
pref-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 455 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.
build
Run full verification pipeline.
generate-rules
Generate development rules and standards into RULES.md.
feedback
File a plugin-capability-gap note, or flush queued notes to GitHub issues.
prd
Generate a Product Requirements Document for an team squad. Business-facing artifact. Sensors and evals gate.