backup

A command that creates a backup copy of the central Gnosys database and related files.

In plain words
What is it for?
Use it to save backups in a chosen directory, include the sandbox log when present, and view the backup result as human-readable text or JSON.
Why use it?
It protects stored memories and project information so they can be recovered if the working database is lost or damaged.

Command

Install

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.

agentmods
npx agentmods add commands/proticom/gnosys/backup
Clone the repo
git clone --depth 1 https://github.com/proticom/gnosys
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 523 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What 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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00523
Opus 5 $0.00000 $0.00262
Sonnet 5 $0.00000 $0.00105
Haiku 4.5 $0.00000 $0.00052

Measured 2d ago against content hash 4309a35b4788, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

backup 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.

docs/commands/backup.md · 90 lines

What it actually says

gnosys backup

Create a backup of the central Gnosys database and related files.

Usage

gnosys backup
gnosys backup --output ./backups
gnosys backup --to ./backups
gnosys backup --json

Options

Option Description
-o, --output <dir> Backup output directory (default: ~/.gnosys/)
--to <dir> Alias for --output
--json Output result as JSON

Behavior

  1. Opens the central DB via GnosysDB.openCentral().
  2. Calls centralDb.backup(outputDir) where outputDir is --to or --output if set.
  3. Collects memory and project counts from the central DB.
  4. Copies sandbox/sandbox.log to sandbox.log.bak in the backup directory when the log exists.
  5. Prints human-readable success output or JSON.
  6. Closes the central DB in finally.

Output modes

Human (default):

Backup created: /path/to/backup.db
  Memories: 42 (40 active, 2 archived)
  Projects: 3
  Additional files: 1

JSON (--json):

{
  "ok": true,
  "backupPath": "/path/to/backup.db",
  "memories": 42,
  "active": 40,
  "archived": 2,
  "projects": 3,
  "files": ["/path/to/backup.db", "/path/to/sandbox.log.bak"]
}

Errors

Central DB unavailable:

Central DB not available (better-sqlite3 missing).

Backup failure (human):

Backup failed: <message>

Backup failure (JSON):

{ "ok": false, "error": "<message>" }

Failure paths set process.exitCode = 1 and return through finally so the DB handle is closed.

Validation

cd gnosys-public
npm run cli -- backup --help
npx vitest run src/test/backup-command-handler.test.ts
  • gnosys restore — restore from a backup file.
  • gnosys sync — remote sync of the central DB.
Changes

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.

  1. 2d ago First seen · 90 lines · 0 tokens per session scan A 4309a35b4788

Subscribe to this mod's changes

backup 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 523 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.