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/migrate-dbgit 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.00522 |
| Opus 5 | $0.00000 | $0.00261 |
| Sonnet 5 | $0.00000 | $0.00104 |
| Haiku 4.5 | $0.00000 | $0.00052 |
Grade A, and why
migrate-db 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gnosys migrate-db
Legacy data migration command. Supports per-store v1→v2 migration and optional central DB consolidation.
Usage
gnosys migrate-db
gnosys migrate-db -v
gnosys migrate-db --to-central
gnosys migrate-db --to-central --verbose
Options
| Option | Description |
|---|---|
--to-central |
Migrate all discovered per-project stores into ~/.gnosys/gnosys.db |
-v, --verbose |
Verbose output |
Legacy mode (default)
When --to-central is absent:
- Resolves the writable store via
getResolver(). - Runs
migrate(storePath, { verbose })fromsrc/lib/migrate.js. - Prints
formatMigrationReport(stats).
No writable store:
No writable store found. Run 'gnosys init' first.
Exits with code 1 via process.exitCode.
Central mode (--to-central)
- Opens the central DB via
GnosysDB.openCentral(). - Discovers all registered project stores with
resolver.detectAllStores(). - For each project with
.gnosys:- Creates project identity via
createProjectIdentity. - Opens the per-project DB, imports memories into central DB in a transaction.
- Skips projects without a migrated
gnosys.db.
- Creates project identity via
- Prints a central migration summary.
- Per-project
gnosys.dbfiles are left untouched.
Central DB unavailable:
Central DB not available (better-sqlite3 missing).
Central DB open failure:
Cannot open central DB: <message>
No stores found:
No per-project stores found to migrate.
Per-project errors are logged as ✗ <dir>: <message> without stopping the whole run.
DB cleanup
Central and per-project DB handles close through finally blocks. Expected failures use process.exitCode = 1; return;.
Validation
cd gnosys-public
npm run cli -- migrate-db --help
npx vitest run src/test/migrate-db-command-handler.test.ts
Related commands
gnosys migrate— interactive project directory migration.gnosys init— initialize a project store before legacy migration.
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 · 84 lines · 0 tokens per session scan A 3064be55a784
migrate-db 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 522 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.