init

A command that registers the current project with the cix code index, scans its files, and starts a watcher that updates the index when files change.

In plain words
What is it for?
Use it when setting up cix for a project, then check its status if indexing fails or is still running.
Why use it?
It gives cix an up-to-date view of the project so its code search or analysis can work from current files.

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/dvcdsys/code-index/init
Clone the repo
git clone --depth 1 https://github.com/dvcdsys/code-index
Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 145 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.00019 $0.00145
Opus 5 $0.00010 $0.00072
Sonnet 5 $0.00004 $0.00029
Haiku 4.5 $0.00002 $0.00015

Measured yesterday against content hash 215220b61d7f, 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.

plugins/cix/commands/init.md · 18 lines

What it actually says

Initialize the cix index for the current project. This registers the project with the cix server, performs a full initial index, and starts the file-watcher daemon for auto-reindex on changes.

cix init

If the indexing run is in-progress, you can monitor it with /cix:status. If it fails, common causes are: cix-server not reachable, missing CIX_API_KEY env var, or ~/.cix/data permission issues. Check cix status for details.

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 · 18 lines · 19 tokens per session scan A 215220b61d7f

Subscribe to this mod's changes

init is a command published in the GitHub repository dvcdsys/code-index (29 stars, last pushed 4d ago), licensed MIT. It adds 19 tokens to every session and 145 once invoked, about $0.0001 per session on Opus 5. 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-30.