init

A command for creating or re-syncing a Gnosys project store in a directory. A project store is the local Gnosys data and configuration associated with a code project.

In plain words
What is it for?
Use it to initialize a new project, update an existing .gnosys directory, assign a project name, and prepare IDE integration.
Why use it?
It sets up the files and registration needed for Gnosys to recognize the project, while also connecting supported IDE hooks when present.

Command

Install

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.

agentmods
npx agentmods add commands/proticom/gnosys/init
Clone the repo
git clone --depth 1 https://github.com/proticom/gnosys
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 612 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00612
Opus 5 $0.00000 $0.00306
Sonnet 5 $0.00000 $0.00122
Haiku 4.5 $0.00000 $0.00061

Measured yesterday against content hash 7069032eae27, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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 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.

docs/commands/init.md · 65 lines

How it starts

The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.

gnosys init

Initialize or re-sync a Gnosys project store in the target directory.

Usage

gnosys init
gnosys init --directory ./path/to/project
gnosys init --name "Project Name"
gnosys init -d ./apps/api -n "Mavenn API"

Options

  • -d, --directory <dir> — Target directory. Defaults to the current working directory.
  • -n, --name <name> — Project name. Defaults to the target directory basename.

Behavior

  • Creates .gnosys/ when it does not exist (first-time init).
  • Re-syncs identity and registration when .gnosys/ already exists.
  • Creates project identity and registers the project in the central DB when available.
  • Adds .gnosys/ to the project .gitignore.
  • Configures supported IDE hooks when .claude/, .cursor/, or .codex/ is detected.
  • Prints the follow-up gnosys setup ides command for MCP wiring.

Writes and side effects

  • Creates .gnosys/.config/, tag registry, config template, attachments manifest, and .gnosys/.gitignore on first init.
  • Writes or updates project identity metadata (gnosys.json).
  • Registers the project in the file-based project registry and central DB when available.
  • May update IDE hook files under the project (Claude Code, Cursor, Codex, etc.).
  • May append .gnosys/ to the project root .gitignore.

Platform notes

macOS

  • Project store: <target-dir>/.gnosys/
  • Central DB: ~/.gnosys/gnosys.db when available
  • IDE hooks: Detects ~/.../project/.cursor, .claude, or .codex and writes hook configs accordingly
  • Paths: Use forward slashes; ~ expands in shell examples

Linux

  • Project store: <target-dir>/.gnosys/
  • Central DB: ~/.gnosys/gnosys.db when available
  • IDE hooks: Same detection as macOS under the project directory
  • Paths: Standard XDG layout; config under ~/.gnosys/ for global settings

Windows

  • Project store: <target-dir>\.gnosys\ (or mixed paths via Node path APIs)
  • Central DB: Under user profile ~/.gnosys/gnosys.db
  • IDE hooks: Detects .cursor, .claude, or .codex in the project folder
  • Paths: PowerShell accepts both \ and /; prefer quoted paths with spaces

Read the full file on GitHub · 65 lines

Changes

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.

  1. yesterday First seen · 65 lines · 0 tokens per session scan A 7069032eae27

Subscribe to this mod's changes

init 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 612 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.