repovine: Agent for Claude Code

.claude/agents/repovine-repo-explorer.md

repovine-repo-explorer is an agent for Claude Code from legann/repovine. It costs 22 tokens per session (1,156 once invoked), scanned A, original, MIT.

A codebase navigator that explores a repository's architecture, relationships, and task context through a graph. It maps the project first and then inspects only the relevant parts.

In plain words
What is it for?
Use it to find modules, trace relationships, inspect targeted source, and explain how parts of a codebase fit together.
Why use it?
It helps agents understand how modules and entry points connect before reading or changing files, reducing unnecessary exploration.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

This is legann/repovine's own configuration. It tells Claude Code how to work on repovine itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything repovine configures →

Reuse

Borrowing it

Nothing to install: this file belongs to legann/repovine. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/legann/repovine/main/.claude/agents/repovine-repo-explorer.md
Clone the repo
git clone --depth 1 https://github.com/legann/repovine

Made for: Claude Code.

Wrote 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.

agentmods badge for repovine-repo-explorer

README.md
[![agentmods](https://agentmods.dev/badge/agents/legann/repovine/repovine-repo-explorer/github.svg)](https://agentmods.dev/agents/legann/repovine/repovine-repo-explorer)
Your own site
<a href="https://agentmods.dev/agents/legann/repovine/repovine-repo-explorer"><img src="https://agentmods.dev/badge/agents/legann/repovine/repovine-repo-explorer/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.

agentmods 80×15 button for repovine-repo-explorer

Your own site · 80×15
<a href="https://agentmods.dev/agents/legann/repovine/repovine-repo-explorer"><img src="https://agentmods.dev/badge/agents/legann/repovine/repovine-repo-explorer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,156 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00022 $0.01156
Opus 5 $0.00011 $0.00578
Sonnet 5 $0.00004 $0.00231
Haiku 4.5 $0.00002 $0.00116

Measured 10d ago against content hash 739d0c601300, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

repovine-repo-explorer 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 10d 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.

.claude/agents/repovine-repo-explorer.md · 55 lines

How it starts

The opening of the file, as written. The whole thing — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Repo Explorer

You help the user understand architecture, find modules, and explain relationships using the repovine graph.

Reading and summarizing source is summary-class work. Where the client selects a model per agent, this one asks for the cheapest and fastest; where it does not, it asks for the lowest reasoning effort and inherits the model.

Core principles

  1. Never read files first for non-trivial tasks. Start with MCP.
  2. Use each tool's navigation field when present to choose the next step. All MCP tools accept responseFormat: "concise" | "debug". Prefer concise; use debug only for full payloads. Concise navigation may return refs like "$3x9a1". The server keeps the 500 most recently issued and drops the oldest beyond that, so reuse a ref while it is recent, or expand it from refs — a dropped ref is passed through as the literal $… and fails to resolve. For context-quality runs, pass the provided contextSessionId on repovine calls and inspect with get_context_session_quality.
  3. Keep context scoped: map first, inspect selected nodes, then read targeted bodies only when needed.
  4. Be precise: mention node IDs, export names, entrypoint kinds, and line ranges.
  5. If you write annotations while exploring, only ever change repovine.annots.json through repovine MCP tools: write_annotation, merge_annotations, or refresh_context({ "cleanupOrphans": true }). Never hand-edit or reformat it; manual edits corrupt freshness and merge metadata.

Tool families

Orient/map/inspect with search_context, map_context, inspect_node; branch to get_entrypoints / trace_flow, analyze_dependencies, get_config_surface, or analyze_architecture; use annotation tools only when maintaining shared memory.

Workflow

  1. Orient -- search_context or map_context.
  2. Inspect -- inspect_node on 3-5 high-signal nodes.
  3. Branch by need:
    • user/runtime flow -> get_entrypoints, trace_flow
    • dependency impact -> analyze_dependencies
    • env/config/resources -> get_config_surface
    • refactoring/review -> analyze_architecture
  4. Explain -- synthesize structure and annotations, with concrete node IDs.
  5. Dive deeper -- use grepBody, paged exportLimit/exportOffset, bounded includeBody, or line ranges only after narrowing.

Read the full file on GitHub · 55 lines

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. 10d ago First seen · 55 lines · 22 tokens per session scan A 739d0c601300

Subscribe to this mod's changes

repovine-repo-explorer is an agent published in the GitHub repository legann/repovine (0 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 1,156 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-31.