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-projectgit 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.00568 |
| Opus 5 | $0.00000 | $0.00284 |
| Sonnet 5 | $0.00000 | $0.00114 |
| Haiku 4.5 | $0.00000 | $0.00057 |
Grade A, and why
export-project 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gnosys export project
Export a single registered Gnosys project to a portable .json.gz bundle (round-trips with gnosys import project).
Usage
gnosys export project --to ./project.gnosys.json.gz
gnosys export project my-project --to ./project.gnosys.json.gz
gnosys export project my-project --to ./bundle.gnosys.json.gz --include-archived --no-audit --json
When projectId is omitted, the command auto-detects from the current working directory's registry entry.
Options
| Option | Description |
|---|---|
--to <file> |
Output bundle path (required) |
--include-archived |
Include archived and superseded memories (default: active only) |
--no-audit |
Skip audit log in the bundle |
--json |
Output result as JSON |
Behavior
- Opens the central DB via
GnosysDB.openCentral(). - Resolves
projectIdfrom argument orgetProjectByDirectory(process.cwd()). - Calls
exportProject(centralDb, { projectId, outputPath, includeArchived, includeAudit }). - Prints human summary or JSON.
- Closes central DB in
finally.
Human output
Exported project my-project
Memories: 142
Archived: 3 excluded — re-run with --include-archived for a full backup
Relationships: 28
Audit entries: 512
Bundle: /path/to/project.gnosys.json.gz
Size: 45.2 KB compressed (12.3% of 367.1 KB)
JSON output
Full exportProject result object when --json is set.
Errors
Central DB unavailable:
Central DB unavailable.
No project ID and cwd not registered:
No project ID given and current directory is not a registered project.
Usage: gnosys export project <projectId> --to <file>
Validation failures after DB open use process.exitCode = 1.
Validation
cd gnosys-public
npm run cli -- export project --help
npx vitest run src/test/export-command-handler.test.ts
node scripts/audit-commands.mjs --write
Related commands
gnosys export— parent command overview.gnosys export vault— Obsidian markdown vault export.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 · 79 lines · 0 tokens per session scan A 00a8791d4565
export-project 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 568 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.