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/dvcdsys/code-index/treegit clone --depth 1 https://github.com/dvcdsys/code-indexWhat 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.00016 | $0.00191 |
| Opus 5 | $0.00008 | $0.00096 |
| Sonnet 5 | $0.00003 | $0.00038 |
| Haiku 4.5 | $0.00002 | $0.00019 |
Grade A, and why
tree 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.
What it actually says
List one level of a directory (ls-like, no recursion) in the server-side checkout of an external (GitHub-backed) cix project: $ARGUMENTS
cix tree $ARGUMENTS
This works only for external / workspace repos the server keeps on disk — use it
to navigate the file tree of a repo you don't have locally before reading a file
with /cix:file. For the current / local project, use the native ls/Read
tools instead.
Tips:
- Target the repo with
-n github.com/owner/repo@main(fromcix list). - Omit the directory argument to list the repository root.
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.
- yesterday First seen · 22 lines · 16 tokens per session scan A 8c340a4ae9d8
tree is a command published in the GitHub repository dvcdsys/code-index (29 stars, last pushed 4d ago), licensed MIT. It adds 16 tokens to every session and 191 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.
Other commands, from other repositories
prime
Re-prime the agent's context with the current tea-rags index state for this project.
merge
Finalize work on a branch: verify docs + tree are clean, merge to main, clean up. Supports both standard git checkout -b branches and git worktree flows — auto-detected at pre-flight.
dev
Runs Vendure in development mode. By default it starts three processes: the GraphQL server (ts-node ./src/index.ts), the worker (ts-node ./src/index-worker.ts), and the dashboard (a Vite dev server).
start
Runs a project that has already been compiled with vendure build.
codesage-reindex
Force an incremental codesage re-index (use when git hooks didn't fire). Auto-cleans orphan vec tables if the config model has changed.
pipeline-undo
Undo a pipeline run's result. With worktree isolation (the current engine), this is clean and low-risk: a run never touches your checkout — its result lives only on a pipeline/ branch (and, for a --push run, on the remote). "Undo" therefore means deleting that branch and its worktree, not reverting your working tree.