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-showgit 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.00633 |
| Opus 5 | $0.00000 | $0.00316 |
| Sonnet 5 | $0.00000 | $0.00127 |
| Haiku 4.5 | $0.00000 | $0.00063 |
Grade A, and why
machine-show 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gnosys machine show
Show this machine's local machine.json configuration (machineId, hostname, roots, remote).
Usage
gnosys machine show
gnosys machine show --json
Options
| Option | Description |
|---|---|
--json |
Output the machine config object as JSON |
Behavior
- Reads
machine.jsonviareadMachineConfig(). - If missing, prints the expected path from
getMachineConfigPath()and suggestsgnosys machine migrateorgnosys scan. - Otherwise prints human summary or JSON via
outputResult.
Human output
machine.json: /Users/you/.gnosys/machine.json
machineId: abc123...
hostname: my-mac
roots: {"dev":"/Users/you/projects"}
## Platform notes
### macOS
- Path: `~/.gnosys/machine.json` (or `$GNOSYS_HOME/machine.json`).
- Never synced (machine-local only for network topologies).
- Launchd jobs for serve or sync read this for machineId/roots.
### Linux
- Same as macOS (`~/.gnosys/machine.json`).
- systemd units use the roots and machineId from here.
### Windows
- Path: `%APPDATA%\gnosys\machine.json` or `%LOCALAPPDATA%\gnosys\machine.json`.
- Credential Manager / env for related keys; machine.json for identity and roots.
- WSL: may see Unix paths; the Windows gnosys binary uses the Windows location.
## Related (network + multi-machine)
- `gnosys machine migrate`, `machine list`, `machine forget` for managing the config.
- `gnosys scan` to (re)populate roots.
- `gnosys centralize` and `connect` for the network-hosted flow that relies on stable per-machine identity.
- `gnosys setup remote` for sync against a central brain.
remote: (disabled)
When remote is enabled with a path:
remote: /Volumes/NAS/gnosys-remote
JSON output
With --json, emits the full normalized machine config object.
Missing config
No machine.json yet (/Users/you/.gnosys/machine.json).
Run 'gnosys machine migrate' (existing setup) or 'gnosys scan' to create it.
Validation
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 · 87 lines · 0 tokens per session scan A 9ed38da518db
machine-show 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 633 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.