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/restoregit 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.00444 |
| Opus 5 | $0.00000 | $0.00222 |
| Sonnet 5 | $0.00000 | $0.00089 |
| Haiku 4.5 | $0.00000 | $0.00044 |
Grade A, and why
restore 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 restore
Restore the central Gnosys database from a backup file.
Usage
gnosys restore ./gnosys-backup-20260528.db
gnosys restore backup-placeholder --from ./gnosys-backup-20260528.db
gnosys restore ./gnosys-backup-20260528.db --json
Options
| Option | Description |
|---|---|
--from <file> |
Backup file to restore from (overrides positional <backupFile>) |
--json |
Output result as JSON |
Behavior
- Resolves the backup path:
path.resolve(opts.from || backupFile). - Calls
GnosysDB.restore(resolved)to replace the central DB from the backup. - Reads memory and project counts from the restored DB.
- Prints human-readable success output or JSON.
- Closes the restored DB handle in
finally.
Output modes
Human (default):
Database restored from /path/to/backup.db
Memories: 42 (40 active, 2 archived)
Projects: 3
JSON (--json):
{
"ok": true,
"source": "/path/to/backup.db",
"memories": 42,
"active": 40,
"archived": 2,
"projects": 3
}
Errors
Restore failure (human):
Restore failed: <message>
Restore 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 -- restore --help
npx vitest run src/test/restore-command-handler.test.ts
Related commands
gnosys backup— create a central DB backup.gnosys sync— remote sync of the central DB.
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 02d28ec57210
restore 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 444 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.