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/config-initgit 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.00451 |
| Opus 5 | $0.00000 | $0.00226 |
| Sonnet 5 | $0.00000 | $0.00090 |
| Haiku 4.5 | $0.00000 | $0.00045 |
Grade A, and why
config-init 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 config init
Generate a blank gnosys.json template in the active writable store.
Deprecated: prefer gnosys setup for interactive configuration.
Usage
gnosys config init
gnosys config init --force
Behavior
- Without
--force: prints a deprecation warning pointing tognosys setup, then exits without writing any file. - With
--force: writes a blank config template to<writable-store>/gnosys.jsonwhen that file does not already exist. - Exits with
No writable store found.when no writable store is available. - Exits with
gnosys.json already exists. Use 'gnosys config set' to modify.when the target config file is already present. - On success with
--force, printsCreated <path>.
Output example (default, no --force)
gnosys config init
! writing a blank template means the next run of `gnosys setup`
! will walk you through the same choices anyway
try gnosys setup interactive walkthrough (recommended)
re-run with --force to write the template anyway
Platform notes
macOS
- Writable store is typically project
./.gnosysor personal~/.gnosys. - Template is written as
gnosys.jsoninside the store directory.
Linux
- Same store resolution as macOS. Run
gnosys initfirst if no stores exist.
Windows
- Paths in success/error messages may use backslashes; behavior is the same as on Unix.
- Prefer
gnosys setupon all platforms for first-time configuration.
Validation
cd gnosys-public
npm run cli -- config init --help
npm run cli -- config init
npm run cli -- config init --force
Related commands
gnosys setup— recommended interactive walkthrough (replaces plainconfig init).gnosys config set— modify an existinggnosys.json.
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 · 64 lines · 0 tokens per session scan A 03b5a5bdd4b2
config-init 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 451 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.