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/exportgit 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.00660 |
| Opus 5 | $0.00000 | $0.00330 |
| Sonnet 5 | $0.00000 | $0.00132 |
| Haiku 4.5 | $0.00000 | $0.00066 |
Grade A, and why
export 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.
How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gnosys export
Export Gnosys memory to an Obsidian-compatible vault or a portable project bundle.
Usage
gnosys export
gnosys export vault --to ./vault
gnosys export --to ./vault
gnosys export project --to ./project.gnosys.json.gz
gnosys export project <projectId> --to ./project.gnosys.json.gz
Bare gnosys export prints usage and exits with code 1.
Subcommands
| Subcommand | Purpose |
|---|---|
vault |
Export store to Obsidian-compatible markdown vault |
project [projectId] |
Export a single project to .json.gz bundle |
Legacy shim
gnosys export --to <dir> is rewritten to gnosys export vault --to <dir> before parsing (v5.5.x compatibility).
gnosys export vault
gnosys export vault --to ./vault
gnosys export vault --to ./vault --all --overwrite --json
| Option | Description |
|---|---|
--to <dir> |
Target directory (required) |
--all |
Export active + archived memories |
--overwrite |
Overwrite existing files |
--no-summaries |
Skip category summaries |
--no-reviews |
Skip review suggestions |
--no-graph |
Skip relationship graph |
--json |
Output raw JSON report |
Requires a migrated project store (gnosys.db v2.0).
gnosys export project
gnosys export project --to ./bundle.gnosys.json.gz
gnosys export project my-project --to ./bundle.gnosys.json.gz --include-archived --no-audit --json
| Option | Description |
|---|---|
--to <file> |
Output bundle path (required) |
--include-archived |
Include archived/superseded memories |
--no-audit |
Skip audit log in bundle |
--json |
Output result as JSON |
When projectId is omitted, auto-detects from the current working directory registry entry.
Errors
No stores (vault):
No Gnosys stores found. Run 'gnosys init' first.
Unmigrated DB (vault):
Export requires gnosys.db (v2.0). Run 'gnosys migrate' first.
Central DB unavailable (project):
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 · 101 lines · 0 tokens per session scan A 991ed3633069
export is a command published in the GitHub repository proticom/gnosys (4 stars, last pushed 15d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 660 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.