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/helpergit 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.00390 |
| Opus 5 | $0.00000 | $0.00195 |
| Sonnet 5 | $0.00000 | $0.00078 |
| Haiku 4.5 | $0.00000 | $0.00039 |
Grade A, and why
helper 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 helper
Parent command for generating a tiny TypeScript helper library that agents import to talk to the Gnosys sandbox directly. Pairs with gnosys sandbox start — agents call memory operations like normal code instead of issuing MCP tool calls on every operation.
Usage
gnosys helper
gnosys helper generate
gnosys helper generate --directory ./agent
Bare gnosys helper (no subcommand) prints Commander help for the available subcommands. The parent command has no runtime .action(...) — all behavior lives in the leaf subcommand below.
Subcommands
| Subcommand | Purpose |
|---|---|
generate |
Write gnosys-helper.ts in the target directory |
See the leaf command doc for options, output, and error handling:
Sandbox relationship
Typical workflow:
- Start the sandbox:
gnosys sandbox start - Generate the helper in your agent project:
gnosys helper generate - Import
gnosys-helper.tsfrom agent scripts for low-latencyadd/recallcalls
Most users do not need the sandbox or helper; MCP via gnosys serve is the default integration path.
Validation
cd gnosys-public
npm run cli -- helper --help
npx vitest run src/test/helper-command-handler.test.ts
node scripts/audit-commands.mjs --write
Related commands
gnosys sandbox— parent command for the background sandbox processgnosys sandbox start— start the sandbox before generating the helpergnosys serve— MCP server mode (alternative integration path)
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 · 49 lines · 0 tokens per session scan A 903a6f4fda7c
helper 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 390 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.