def

A command that finds where a named function, type, or other code symbol is defined in an indexed codebase. If several definitions match, it helps choose the likely one.

In plain words
What is it for?
Use it for go-to-definition work; if the exact definition is not found, search the index for matching symbol names.
Why use it?
It reduces the time spent searching through files when you need to understand or change existing code.

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/def
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 125 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.00125
Opus 5 $0.00009 $0.00063
Sonnet 5 $0.00003 $0.00025
Haiku 4.5 $0.00002 $0.00013

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

Security

Grade A, and why

def 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/def.md · 16 lines

What it actually says

Look up the definition of the symbol $ARGUMENTS in the cix index:

cix definitions $ARGUMENTS

If multiple matches are returned, point out the most likely one based on context. If nothing is found, suggest cix symbols $ARGUMENTS for a broader name search.

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 · 16 lines · 17 tokens per session scan A 4ae84baa2aab

Subscribe to this mod's changes

def 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 125 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.