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/gemini-cli-extensions/lookerWrote 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/gemini-cli-extensions/looker/gemini-extension)<a href="https://agentmods.dev/plugins/gemini-cli-extensions/looker/gemini-extension"><img src="https://agentmods.dev/badge/plugins/gemini-cli-extensions/looker/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/gemini-cli-extensions/looker/gemini-extension"><img src="https://agentmods.dev/badge/plugins/gemini-cli-extensions/looker/gemini-extension.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
looker 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 1mo 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.
What it actually says
{
"name": "looker",
"version": "0.3.11",
"description": "Connect to Looker and interact with your data using LookML.",
"mcpServers": {
"looker": {
"command": "npx",
"args": [
"-y",
"@toolbox-sdk/[email protected]",
"--prebuilt",
"looker",
"--stdio"
]
},
"looker-dev": {
"command": "npx",
"args": [
"-y",
"@toolbox-sdk/[email protected]",
"--prebuilt",
"looker-dev",
"--stdio"
]
}
},
"contextFileName": "LOOKER.md",
"settings": [
{
"name": "Base URL",
"description": "URL of the Looker instance",
"envVar": "LOOKER_BASE_URL"
},
{
"name": "Client ID",
"description": "Client ID of the Looker API",
"envVar": "LOOKER_CLIENT_ID"
},
{
"name": "Client Secret",
"description": "Client Secret of the Looker API",
"envVar": "LOOKER_CLIENT_SECRET"
},
{
"name": "Verify SSL",
"description": "(Optional) Boolean to verify SSL certificates",
"envVar": "LOOKER_VERIFY_SSL"
},
{
"name": "Show Hidden Models",
"description": "(Optional) Boolean to show hidden models",
"envVar": "LOOKER_SHOW_HIDDEN_MODELS"
},
{
"name": "Show Hidden Explores",
"description": "(Optional) Boolean to show hidden explores",
"envVar": "LOOKER_SHOW_HIDDEN_EXPLORES"
},
{
"name": "Show Hidden Fields",
"description": "(Optional) Boolean to show hidden fields",
"envVar": "LOOKER_SHOW_HIDDEN_FIELDS"
}
]
}
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.
- 1mo ago First seen · 66 lines scan A a36d9000a8c1
looker is a plugin published in the GitHub repository gemini-cli-extensions/looker (57 stars, last pushed 1mo ago), 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-12.
Other plugins, from other repositories
cloud-sql-postgresql
Create, connect, and interact with a Cloud SQL for PostgreSQL database and data.
cloud-sql-postgresql
Create, connect, and interact with a Cloud SQL for PostgreSQL database and data.
knowledge-catalog
Connect to Knowledge Catalog to discover, manage, monitor, and govern data and AI artifacts across your data platform.
firestore-native
Connect and interact with Firestore databases, collections, and documents.
knowledge-catalog
Connect to Knowledge Catalog to discover, manage, monitor, and govern data and AI artifacts across your data platform.
firestore-native
Connect and interact with Firestore databases, collections, and documents.