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/export-vaultgit 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.00530 |
| Opus 5 | $0.00000 | $0.00265 |
| Sonnet 5 | $0.00000 | $0.00106 |
| Haiku 4.5 | $0.00000 | $0.00053 |
Grade A, and why
export-vault 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 export vault
Export the current Gnosys project store to an Obsidian-compatible markdown vault.
Usage
gnosys export vault --to ./vault
gnosys export --to ./vault
gnosys export vault --to ./vault --all --overwrite --json
Legacy gnosys export --to <dir> is rewritten to gnosys export vault --to <dir> before parsing.
Options
| Option | Description |
|---|---|
--to <dir> |
Target directory for export (required) |
--all |
Export active + archived memories |
--overwrite |
Overwrite existing files in the target |
--no-summaries |
Skip category summaries |
--no-reviews |
Skip review suggestions |
--no-graph |
Skip relationship graph export |
--json |
Output raw JSON report instead of formatted text |
Behavior
- Resolves configured stores via
GnosysResolver. - Opens the primary store DB and verifies
gnosys.dbis migrated (v2.0). - Runs
GnosysExporter.export()with option mapping. - Prints progress on stderr during export.
- Prints
formatExportReport(report)or JSON to stdout.
Progress example:
Exporting to: /path/to/vault
[10/42] memories/architecture/example.md
Prerequisites
- At least one Gnosys store (run
gnosys initfirst). - Migrated
gnosys.db(rungnosys migrateif needed).
Errors
No stores:
No Gnosys stores found. Run 'gnosys init' first.
Unmigrated DB:
Export requires gnosys.db (v2.0). Run 'gnosys migrate' first.
Exits with code 1 on validation failures after DB open uses process.exitCode.
Validation
cd gnosys-public
npm run cli -- export vault --help
npx vitest run src/test/export-command-handler.test.ts
node scripts/audit-commands.mjs --write
Related commands
gnosys export— parent command overview (vault + project).gnosys export project— portable.json.gzproject bundle.gnosys import project— restore a project bundle.
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 · 77 lines · 0 tokens per session scan A 1f5cbc9dc7e6
export-vault 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 530 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.