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/machinegit 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.00487 |
| Opus 5 | $0.00000 | $0.00244 |
| Sonnet 5 | $0.00000 | $0.00097 |
| Haiku 4.5 | $0.00000 | $0.00049 |
Grade A, and why
machine 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 yesterday.
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
Parent command for managing this machine's local config (machine.json: machineId, roots, remote).
Machine-local settings stay on each host and are not synced through the central DB. Use this command to inspect or migrate that config.
Usage
gnosys machine
gnosys machine show
gnosys machine show --json
gnosys machine migrate
gnosys machine migrate --root /Users/you/projects --no-scan
Bare gnosys machine (no subcommand) prints Commander help for the available subcommands. The parent command has no runtime .action(...) — all behavior lives in the leaf subcommands below.
Subcommands
| Subcommand | Purpose |
|---|---|
show |
Show this machine's machine.json |
migrate |
Move machine-local config out of the synced DB into machine.json, set roots, and scan |
gnosys machine show
Displays machineId, hostname, roots, and remote settings from machine.json. With --json, outputs the config object as JSON via outputResult.
If machine.json does not exist yet, prints the expected path and hints to run gnosys machine migrate or gnosys scan.
gnosys machine migrate
Reads machine-local fields from the central DB, writes machine.json, optionally sets a dev root (--root), and scans for projects unless --no-scan is set. Requires an available central DB (GnosysDB.openLocal()).
Platform / path notes
machine.json lives at the path returned by getMachineConfigPath() (under the gnosys home directory for this machine). Roots map logical names (e.g. dev) to absolute directories on this host.
Validation
cd gnosys-public
npm run cli -- machine --help
npx vitest run src/test/machine-command-handler.test.ts
node scripts/audit-commands.mjs --write
Related commands
gnosys scan— discover projects under configured rootsgnosys setup remote— configure remote syncgnosys connect— point an IDE at a remote MCP server
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.
- yesterday First seen · 54 lines · 0 tokens per session scan A db414c2e832d
machine 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 487 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.