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/migrategit 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.00495 |
| Opus 5 | $0.00000 | $0.00247 |
| Sonnet 5 | $0.00000 | $0.00099 |
| Haiku 4.5 | $0.00000 | $0.00049 |
Grade A, and why
migrate 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gnosys migrate
Interactively migrate a .gnosys/ store to a new directory. Moves files, updates project identity, optionally syncs to the central DB, and can remove the old store.
Usage
gnosys migrate
gnosys migrate --from /old/project --to /new/project --name "New Project" --yes
Options
| Option | Description |
|---|---|
--from <dir> |
Source directory containing .gnosys/ (skips prompt) |
--to <dir> |
Target directory where .gnosys/ should live (skips prompt) |
--name <name> |
New project name (skips prompt; default: basename of target) |
--yes |
Skip all confirmation prompts (non-interactive mode) |
Interactive flow
- Resolve source directory (auto-detect from cwd or prompt).
- Verify
.gnosys/exists and show memory file count. - Resolve target directory and project name.
- Ask whether to sync memories to central DB and delete the old store (defaults yes).
- Show summary and confirm before proceeding.
With --yes, sync and delete default to yes; name defaults to target basename.
Behavior
- Validates source store via
readProjectIdentityand markdown glob under.gnosys/. - Opens central DB when available via
GnosysDB.openCentral(). - Runs
migrateProject({ sourcePath, targetPath, newName, deleteSource, centralDb }). - Optionally syncs markdown memories with
syncMemoryToDbafter migration. - Closes readline and central DB in
finally, including error paths.
Output
Migration progress, copied file count, new project identity, central DB status, sync count, and completion message.
Errors
Missing source/target, missing .gnosys/, migration failures, or sync errors print Migration failed: ... and exit with code 1.
Validation
cd gnosys-public
npm run cli -- migrate --help
npx vitest run src/test/migrate-command-handler.test.ts
Related commands
gnosys projects— verify registered projects after migration.gnosys setup remote sync— remote sync after local 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 · 59 lines · 0 tokens per session scan A 0ff941ba2721
migrate 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 495 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.