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.
git clone --depth 1 https://github.com/dvcdsys/code-indexWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/dvcdsys/code-index/tree)<a href="https://agentmods.dev/commands/dvcdsys/code-index/tree"><img src="https://agentmods.dev/badge/commands/dvcdsys/code-index/tree/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/dvcdsys/code-index/tree"><img src="https://agentmods.dev/badge/commands/dvcdsys/code-index/tree.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00016 | $0.00191 |
| Opus 5.5 | $0.00006 | $0.00076 |
| Sonnet 5.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 1mo 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
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.
- 1mo ago First seen · 22 lines · 16 tokens per session scan A 8c340a4ae9d8
tree is a command published in the GitHub repository dvcdsys/code-index (30 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.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
map
Redo the portfolio view and the cross-repo map.
study
Study one or more repos and write their knowledge docs.
refresh
Find docs older than their code, and restudy those.
prime
Re-prime the agent's context with the current tea-rags index state for this project.
index
Index or reindex this repository with jarvis so structural queries work.
status
Report whether this repository is indexed, fresh, and which jarvis tools are available.