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/machine-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.00524 |
| Opus 5 | $0.00000 | $0.00262 |
| Sonnet 5 | $0.00000 | $0.00105 |
| Haiku 4.5 | $0.00000 | $0.00052 |
Grade A, and why
machine-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.
What it actually says
gnosys machine migrate
Move machine-local config (machineId, remote path) out of the synced central DB into this host's machine.json, optionally set the dev root, and scan for projects.
Usage
gnosys machine migrate
gnosys machine migrate --root /Users/you/projects
gnosys machine migrate --root /Users/you/projects --no-scan
Options
| Option | Description |
|---|---|
--root <dir> |
Set this machine's dev root (default: derived from the project registry) |
--no-scan |
Skip the project scan after writing machine.json |
Behavior
- Opens the central DB via
GnosysDB.openLocal(). - Calls
migrateMachine(db, { root: opts.root, scan: opts.scan }). - Writes
machine.jsonatgetMachineConfigPath(). - Adopts or regenerates
machineIdand may adoptremote_pathfrom synced DB meta (removed from shared DB when adopted). - Configures roots (including optional
--rootfordev). - Scans projects under roots unless
--no-scan. - Closes the DB after migration.
Success output
✓ machine.json written: /Users/you/.gnosys/machine.json
machineId: abc123... (adopted from synced meta)
remote: adopted remote_path from synced meta (removed from shared DB)
roots: {"dev":"/Users/you/projects"}
scanned 3 project(s):
my-app [registered] /Users/you/projects/my-app
When scan is skipped:
(scan skipped — set a root in machine.json, then run 'gnosys scan')
Errors
Central DB unavailable:
Central DB not available (better-sqlite3 missing).
Exits with code 1.
Validation
cd gnosys-public
npm run cli -- machine migrate --help
npx vitest run src/test/machine-command-handler.test.ts
node scripts/audit-commands.mjs --write
Related commands
gnosys machine— parent command overviewgnosys machine show— display currentmachine.jsongnosys scan— discover projects under configured roots
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 · 71 lines · 0 tokens per session scan A 9063497d5856
machine-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 524 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.