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/sandbox-startgit clone --depth 1 https://github.com/proticom/gnosysWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/proticom/gnosys/sandbox-start)<a href="https://agentmods.dev/commands/proticom/gnosys/sandbox-start"><img src="https://agentmods.dev/badge/commands/proticom/gnosys/sandbox-start.svg" alt="Measured on agentmods" height="20"></a>What 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.00352 |
| Opus 5 | $0.00000 | $0.00176 |
| Sonnet 5 | $0.00000 | $0.00070 |
| Haiku 4.5 | $0.00000 | $0.00035 |
Grade A, and why
sandbox-start 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 3d 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 sandbox start
Start the Gnosys sandbox background process for low-latency agent access to memory operations.
Usage
gnosys sandbox start
gnosys sandbox start --db-path /path/to/db
gnosys sandbox start --persistent --json
Options
| Option | Description |
|---|---|
--persistent |
Keep running across reboots (reserved/future use) |
--db-path <path> |
Custom database directory for the sandbox server |
--json |
Output result as JSON |
Behavior
- Calls
startSandbox({ persistent, dbPath, wait: true }). - Reuses an already-running sandbox when possible.
- Waits for readiness, then prints the process ID.
Human output
Gnosys sandbox running (pid: 12345)
JSON output
Success:
{
"ok": true,
"pid": 12345
}
Failure:
{
"ok": false,
"error": "error message"
}
On failure without --json, prints Failed to start sandbox: ... to stderr and exits with code 1.
Validation
cd gnosys-public
npm run cli -- sandbox start --help
npx vitest run src/test/sandbox-start-command-handler.test.ts
Related commands
gnosys sandbox stop— stop the background process.gnosys sandbox status— check whether the sandbox is running.gnosys helper generate— generate the agent helper library for sandbox access.
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.
- 3d ago First seen · 68 lines · 0 tokens per session scan A d19f905db4dc
sandbox-start is a command published in the GitHub repository proticom/gnosys (4 stars, last pushed 17d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 352 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.
build
Run full verification pipeline.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
generate-rules
Generate development rules and standards into RULES.md.
config
Command "config" from sdebruyn/fabric-dw-mcp-cli, covering configuration & defaults, http retry budget, sql retry budget, mcp workspace allowlist {#mcp-workspace-allowlist} and mcp server log level.