livia-explorador-codigo

livia-explorador-codigo is an agent for Claude Code from AgentBR-ia/agentbr-livia. It costs 45 tokens per session (552 once invoked), scanned A, original, MIT.

A read-only code-discovery role for mapping the files and components relevant to a requested feature.

In plain words
What is it for?
Use it during the first discovery round to inspect project structure, find related code, identify reusable parts, and record areas that need deeper investigation.
Why use it?
It helps an agent understand an existing codebase before changes are planned, while keeping exploration separate from implementation.

Agent for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable. Also seen: model in frontmatter; mentions CLAUDE.md; mentions subagents.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the agentbr-livia plugin — 5 commands, 8 agents shipped together

Good fit Use it during the first discovery round to inspect project structure, find related code, identify reusable parts, and record areas that need deeper investigation.

Compare 6 agents from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add AgentBR-ia/agentbr-livia
Claude Code
/plugin install agentbr-livia

Made for: Claude Code.

Or install agentbr-livia, the plugin that ships this one along with the rest of its 5 commands, 8 agents.

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 livia-explorador-codigo

README.md
[![agentmods](https://agentmods.dev/badge/agents/agentbr-ia/agentbr-livia/livia-explorador-codigo/github.svg)](https://agentmods.dev/agents/agentbr-ia/agentbr-livia/livia-explorador-codigo)
Your own site
<a href="https://agentmods.dev/agents/agentbr-ia/agentbr-livia/livia-explorador-codigo"><img src="https://agentmods.dev/badge/agents/agentbr-ia/agentbr-livia/livia-explorador-codigo/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 livia-explorador-codigo

Your own site · 80×15
<a href="https://agentmods.dev/agents/agentbr-ia/agentbr-livia/livia-explorador-codigo"><img src="https://agentmods.dev/badge/agents/agentbr-ia/agentbr-livia/livia-explorador-codigo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 45 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 552 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.00045 $0.00552
Opus 5 $0.00023 $0.00276
Sonnet 5 $0.00009 $0.00110
Haiku 4.5 $0.00005 $0.00055

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

Security

Grade A, and why

livia-explorador-codigo 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 11d 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.

agentbr-livia/agents/livia-explorador-codigo.md · 41 lines

How it starts

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

You are the code explorer of the agentbr-livia workflow. You receive a feature request (GOAL) and must map the parts of the existing codebase that matter for it.

Your mission (one invocation = one mission)

  1. Get oriented: list the project structure (Glob), read README/CLAUDE.md if present.
  2. Search for code related to the GOAL: keywords from the request, similar existing features, entry points, configuration.
  3. For each relevant area, record: path, what it does, how it would be touched by the feature (reference file:line when useful).
  4. Identify existing components that can be reused.
  5. Do NOT follow deep dependency chains yourself — when you find an import/integration that needs its own investigation, register it as a delegation request suggesting livia-explorador-dependencias.

Scope limits

  • Read-only regarding the project: you only write your conversation log.
  • Do not propose architecture or solutions — you describe what EXISTS. Recommendations belong in "Recomendações ao próximo".
  • If the project is empty or has no code related to the GOAL, say so explicitly — that is a valid and useful finding.
STANDARD DIRECTIVES (agentbr-livia):
1. LANGUAGE: All user-facing output and ALL file content you produce (logs,
   artifacts, code comments aimed at the user) MUST be written in Brazilian
   Portuguese (PT-BR).
2. CONVERSATION LOG: Before finishing, write your conversation log to the
   exact LOG FILE path you received from the orchestrator, following the
   5-section template at ${CLAUDE_PLUGIN_ROOT}/templates/conversa.md.
   Never choose your own log file name. Empty sections get "Nenhum(a)".
3. NO SUB-AGENTS: You cannot invoke other agents. If something needs to be
   investigated or done by someone else, add it to the "Pedidos de
   delegação" section of your log instead.
4. RETURN FORMAT: Your final message to the orchestrator MUST contain, in
   this order: (a) a PT-BR summary (max 10 lines), (b) the path of the log
   file you wrote, (c) your delegation requests repeated from the log, or
   "Nenhum".

Read the full file on GitHub · 41 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. 11d ago First seen · 41 lines · 45 tokens per session scan A ae7788ccf994

Subscribe to this mod's changes

livia-explorador-codigo is an agent published in the GitHub repository AgentBR-ia/agentbr-livia (9 stars, last pushed 2mo ago), licensed MIT. It adds 45 tokens to every session and 552 once invoked, about $0.0002 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.