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/Yamato-main/gemini-discordWrote 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/yamato-main/gemini-discord/gemini-extension)<a href="https://agentmods.dev/plugins/yamato-main/gemini-discord/gemini-extension"><img src="https://agentmods.dev/badge/plugins/yamato-main/gemini-discord/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/yamato-main/gemini-discord/gemini-extension"><img src="https://agentmods.dev/badge/plugins/yamato-main/gemini-discord/gemini-extension.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
gemini-discord 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 4d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{
"name": "gemini-discord",
"version": "0.1.1",
"description": "Discord bridge for Gemini CLI / ACP agent workflows",
"settings": [
{
"name": "Discord Bot Token",
"description": "Bot token from the Discord Developer Portal.",
"envVar": "DISCORD_BOT_TOKEN",
"sensitive": true
},
{
"name": "Boss Discord User ID",
"description": "Stable numeric Discord user ID for full bridge authority.",
"envVar": "DISCORD_BOSS_USER_ID",
"sensitive": false
},
{
"name": "Discord Server ID",
"description": "ID of the server where the bot is installed.",
"envVar": "DISCORD_SERVER_ID",
"sensitive": false
},
{
"name": "Gemini API Key",
"description": "Recommended non-interactive Gemini API key for daemon child processes.",
"envVar": "GEMINI_API_KEY",
"sensitive": true
},
{
"name": "Use Vertex AI",
"description": "Set to true to authenticate Gemini CLI child processes with Vertex AI.",
"envVar": "GOOGLE_GENAI_USE_VERTEXAI",
"sensitive": false
},
{
"name": "Google API Key",
"description": "Optional Google API key for Vertex AI auth when GOOGLE_GENAI_USE_VERTEXAI=true.",
"envVar": "GOOGLE_API_KEY",
"sensitive": true
},
{
"name": "Google Cloud Project",
"description": "Optional Google Cloud project for Vertex AI auth.",
"envVar": "GOOGLE_CLOUD_PROJECT",
"sensitive": false
},
{
"name": "Google Cloud Location",
"description": "Optional Google Cloud location for Vertex AI auth.",
"envVar": "GOOGLE_CLOUD_LOCATION",
"sensitive": false
}
],
"mcpServers": {
"discord-bridge": {
"command": "node",
"args": ["${extensionPath}${/}dist${/}server.cjs"],
"cwd": "${extensionPath}",
"env": {
"DISCORD_BOT_TOKEN": "${DISCORD_BOT_TOKEN}",
"DISCORD_BOSS_USER_ID": "${DISCORD_BOSS_USER_ID}",
"DISCORD_SEWhat ships with it
3 files beside gemini-extension.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 73 lines scan A 6d816e9e3bc1
gemini-discord is a plugin published in the GitHub repository Yamato-main/gemini-discord (5 stars, last pushed 4d ago), licensed MIT. 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-06.
gemini-discord compared with plugins from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| gemini-discordYamato-main/gemini-discord | Plugin | 5 | 4d ago | MIT | 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 |
| knowledge-cataloggemini-cli-extensions/knowledge-catalog | Plugin | 34 | 1mo ago | Apache-2.0 | A | — | Claude Code |
| spannergemini-cli-extensions/spanner | Plugin | 19 | 1mo ago | Apache-2.0 | A | — | Claude Code |
| prompt-engineering-extensionJsebayhi/prompt-engineering-extension | Plugin | 6 | 19d ago | MIT | A | — | Gemini CLI |
| cloud-sql-sqlservergemini-cli-extensions/cloud-sql-sqlserver | Plugin | 10 | 1mo ago | Apache-2.0 | A | — | Gemini CLI |