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.
git clone --depth 1 https://github.com/rmedranollamas/research-cliWrote 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/plugins/rmedranollamas/research-cli/gemini-extension)<a href="https://agentmods.dev/plugins/rmedranollamas/research-cli/gemini-extension"><img src="https://agentmods.dev/badge/plugins/rmedranollamas/research-cli/gemini-extension/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/plugins/rmedranollamas/research-cli/gemini-extension"><img src="https://agentmods.dev/badge/plugins/rmedranollamas/research-cli/gemini-extension.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
research-cli 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 today.
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.
What it actually says
{
"name": "research-cli",
"version": "0.3.4",
"description": "Deep Research extension using Gemini v1alpha Interactions API",
"settings": [
{
"name": "Gemini API Key",
"description": "API Key with v1alpha/Interactions access",
"envVar": "RESEARCH_GEMINI_API_KEY"
},
{
"name": "Research Model",
"description": "The Gemini Deep Research agent ID to use (default: deep-research-preview-04-2026; max: deep-research-max-preview-04-2026)",
"envVar": "RESEARCH_MODEL"
}
]
}
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.
- today Changed f37400fdf23b
- 16d ago Changed e7d737a1d9a8
- 2mo ago First seen · 18 lines scan A ba5396069e23
research-cli is a plugin published in the GitHub repository rmedranollamas/research-cli (20 stars, last pushed today), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-09-07.
research-cli compared with plugins from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| research-clirmedranollamas/research-cli | Plugin | 20 | today | Apache-2.0 | A | — | Gemini CLI |
| lookergemini-cli-extensions/looker | Plugin | 57 | 1mo ago | Apache-2.0 | A | — | Gemini CLI |
| cloud-sql-postgresqlgemini-cli-extensions/cloud-sql-postgresql | Plugin | 42 | 1mo ago | Apache-2.0 | A | — | Gemini CLI |
| gemini-discordYamato-main/gemini-discord | Plugin | 5 | 4d ago | MIT | A | — | Gemini CLI |
| knowledge-cataloggemini-cli-extensions/knowledge-catalog | Plugin | 34 | 1mo ago | Apache-2.0 | A | — | Claude Code |
| firestore-nativegemini-cli-extensions/firestore-native | Plugin | 30 | 1mo ago | Apache-2.0 | A | — | Claude Code |
| firestore-nativegemini-cli-extensions/firestore-native | Plugin | 30 | 1mo ago | Apache-2.0 | A | — | Gemini CLI |