refs

A codebase search command that finds every use of a named function, class, variable, or other symbol using a cix index.

In plain words
What is it for?
Use it to check what will be affected by a code change, trace how a symbol is used, and spot heavily used or suspicious call sites.
Why use it?
It saves you from searching files one by one and helps reveal important callers or unusual uses.

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/refs
Clone the repo
git clone --depth 1 https://github.com/dvcdsys/code-index
Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 113 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.00017 $0.00113
Opus 5 $0.00009 $0.00056
Sonnet 5 $0.00003 $0.00023
Haiku 4.5 $0.00002 $0.00011

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

Security

Grade A, and why

refs 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/refs.md · 15 lines

What it actually says

Find references to the symbol $ARGUMENTS in the cix index:

cix references $ARGUMENTS

Group the references by file and call out any high-traffic call sites or suspicious usage patterns. If you need fewer results, add --limit 20.

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 · 15 lines · 17 tokens per session scan A c23946c2f769

Subscribe to this mod's changes

refs is a command published in the GitHub repository dvcdsys/code-index (29 stars, last pushed 4d ago), licensed MIT. It adds 17 tokens to every session and 113 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.