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 skills add dvcdsys/code-index --skill cix-workspacegit 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/skills/dvcdsys/code-index/cix-workspace)<a href="https://agentmods.dev/skills/dvcdsys/code-index/cix-workspace"><img src="https://agentmods.dev/badge/skills/dvcdsys/code-index/cix-workspace/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/skills/dvcdsys/code-index/cix-workspace"><img src="https://agentmods.dev/badge/skills/dvcdsys/code-index/cix-workspace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00110 | $0.03047 |
| Opus 5.5 | $0.00044 | $0.01219 |
| Sonnet 5.5 | $0.00022 | $0.00609 |
| Haiku 4.5 | $0.00011 | $0.00305 |
Grade A, and why
cix-workspace 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.
How it starts
The opening of the file, as written. The whole thing — 238 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cix workspace — Cross-Project Research Workflow
Some tasks are not contained in one repo. A request like "wire feature X through the platform" can touch a half-dozen repos in different languages and layers — a service, a shared library, the infra manifests, an API spec. Reading one repo gives you 1/N of the picture, and you don't know which N repos are involved until you look.
cix_workspace_search is the tool for that. It searches every repo in a named
workspace at once and tells you:
- Which repos are actually relevant to this request.
- Which code in those repos is the entry point.
- What changes need to land in each, and in what order.
Those three questions are the goal. Don't jump to implementation before you can answer all three with evidence.
There is no "current repo" here (Cowork has no opened working directory). A workspace groups several indexed repos on a server; infer the task's anchor repo from the request, and let the workspace supply the surrounding repos.
This skill only searches. The
cix_*MCP tools are read-only — there is no MCP tool to create a workspace or link/unlink repos. If the workspace you need doesn't exist yet, an operator sets it up with thecixCLI (cix ws create/add) or the dashboard; here you consume workspaces that already exist.
First: which server hosts the workspace?
A cix connection may reach more than one server (a local box, a remote
corporate backend, …). Each server hosts its own workspaces and projects — a
workspace named platform on one server is unrelated to anything on another.
cix_list_servers lists the configured servers. A workspace and all its repos
live on exactly one server. Decide which server you're on, then be consistent:
pass the same server argument to every call in the flow
(cix_list_workspaces, cix_workspace_search, and the per-project cix_search
drill-downs). Mixing servers mid-workflow silently returns empty or wrong-repo
results, because the project doesn't exist on the other server.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 238 lines · 110 tokens per session scan A ad5e01dc82b2
cix-workspace is a skill published in the GitHub repository dvcdsys/code-index (30 stars, last pushed 9d ago), licensed MIT. It adds 110 tokens to every session and 3,047 once invoked, about $0.0004 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 skills, from other repositories
tilth
Use the tilth CLI for code reading, outlining, search, callers, blast-radius deps, and structural diffs. Activate when the user asks to explore a repo, find a symbol, trace callers, read a file, view a diff, or analyze impact. Prefer tilth over grep/cat/find/ls — one invocation returns AST-aware outlines, definitions…
cymbal
Tree-sitter indexed code navigator. Use the cymbal CLI — not Read, Grep, Glob, or Bash — for finding where symbols are defined, tracing callers and callees, locating interface implementations, understanding the impact of a change, and mapping imports across an existing codebase. Returns precise, token-efficient…
gograph
Go repository intelligence for Claude Code. Use when reading, navigating, editing, reviewing, or refactoring a Go codebase. Exposes 64 query, analysis, and workflow capabilities through the local gograph MCP server, including bounded first-call exploration, AST-aware call graphs, blast-radius analysis, impact, and…
gno
Search local documents, files, notes, and knowledge bases. Index directories, search with BM25/vector/hybrid, get AI answers with citations. Use when user wants to search files, find documents, query notes, look up information in local folders, index a directory, set up document search, build a knowledge base, needs…
valid-skill
Provides guidance for valid skill usage.
InvalidName
Should fall back to directory name.