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/alloydb-observabilityWrote 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/alloydb-observability/gemini-extension)<a href="https://agentmods.dev/plugins/gemini-cli-extensions/alloydb-observability/gemini-extension"><img src="https://agentmods.dev/badge/plugins/gemini-cli-extensions/alloydb-observability/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/alloydb-observability/gemini-extension"><img src="https://agentmods.dev/badge/plugins/gemini-cli-extensions/alloydb-observability/gemini-extension.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
alloydb-observability 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 yesterday.
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": "alloydb-observability",
"version": "0.1.3",
"description": "Manage and monitor database performance and health for AlloyDB for PostgreSQL databases.",
"mcpServers": {
"alloydb_observability": {
"command": "${extensionPath}${/}toolbox",
"args": [
"--prebuilt",
"alloydb-postgres-observability",
"--stdio"
]
}
},
"contextFileName": "ALLOYDB-OBSERVABILITY.md"
}
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.
- yesterday First seen · 17 lines scan A 4dfc930032c8
alloydb-observability is a plugin published in the GitHub repository gemini-cli-extensions/alloydb-observability (7 stars, last pushed 2d 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-11-05.
alloydb-observability compared with plugins from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| alloydb-observabilitygemini-cli-extensions/alloydb-observability | Plugin | 7 | 2d ago | Apache-2.0 | A | — | Gemini CLI |
| mcpgdevopam/MCPg | Plugin | 14 | 3d ago | MIT | A | — | Cursor |
| cloud-sql-postgresqlgemini-cli-extensions/cloud-sql-postgresql | Plugin | 42 | 1mo ago | Apache-2.0 | A | — | Gemini CLI |
| nlqdb-memorynlqdb/nlqdb | Plugin | 2 | today | none | A | — | Claude Code |
| database-managercyperx84/claude-code-plugin-examples | Plugin | 2 | 1y ago | MIT | A | — | Claude Code |
| humanizerblader/humanizer | Plugin | 65k | 9d ago | MIT | A | — | Claude Code |
| claude-plugins-official marketplaceanthropics/claude-plugins-official | Plugin | 46k | today | Apache-2.0 | A | — | Claude Code |