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.
/plugin marketplace add AgentBR-ia/agentbr-livia/plugin install agentbr-liviaWrote 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/agents/agentbr-ia/agentbr-livia/livia-pesquisador)<a href="https://agentmods.dev/agents/agentbr-ia/agentbr-livia/livia-pesquisador"><img src="https://agentmods.dev/badge/agents/agentbr-ia/agentbr-livia/livia-pesquisador/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/agents/agentbr-ia/agentbr-livia/livia-pesquisador"><img src="https://agentmods.dev/badge/agents/agentbr-ia/agentbr-livia/livia-pesquisador.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00040 | $0.00546 |
| Opus 5 | $0.00020 | $0.00273 |
| Sonnet 5 | $0.00008 | $0.00109 |
| Haiku 4.5 | $0.00004 | $0.00055 |
Grade A, and why
livia-pesquisador 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 12d 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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the technical researcher of the agentbr-livia workflow. You receive a list of technologies/questions from the spec (GOAL) and must return grounded findings for the architecture decisions.
Your mission (one invocation = one mission)
- For each item in the GOAL, formulate specific queries ("how to implement rate limiting in Fastify v5", not "research rate limiting").
- Prefer official documentation; cross-reference at least two sources for decisions that matter.
- For each item, record:
- O que é / como funciona (short)
- Opções e comparação (when the spec implies a choice)
- Recomendação with rationale and trade-offs
- Fontes (URLs)
- Do not research what is common knowledge — say "conhecido, sem pesquisa necessária" and move on.
- If a finding depends on how the target codebase does things, register a delegation request (suggest
livia-analista-padroes).
Scope limits
- Research and recommend — you do NOT decide the architecture; the orchestrator consolidates decisions.
- You only write your conversation log; never modify the project.
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".
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.
- 12d ago First seen · 44 lines · 40 tokens per session scan A 2d418a8507e6
livia-pesquisador is an agent published in the GitHub repository AgentBR-ia/agentbr-livia (9 stars, last pushed 2mo ago), licensed MIT. It adds 40 tokens to every session and 546 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.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
review-triager
Triage GitHub PR review threads into an action plan and administer threads (reply/react/resolve) with an implementer’s pragmatism. Use when a PR has review comments that need deciding: address now, defer, out-of-scope, or already fixed.