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/azmym/gemini-pluginWrote 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/azmym/gemini-plugin/gemini-summarizer)<a href="https://agentmods.dev/agents/azmym/gemini-plugin/gemini-summarizer"><img src="https://agentmods.dev/badge/agents/azmym/gemini-plugin/gemini-summarizer/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/azmym/gemini-plugin/gemini-summarizer"><img src="https://agentmods.dev/badge/agents/azmym/gemini-plugin/gemini-summarizer.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.00057 | $0.01493 |
| Opus 5.5 | $0.00023 | $0.00597 |
| Sonnet 5.5 | $0.00011 | $0.00299 |
| Haiku 4.5 | $0.00006 | $0.00149 |
Grade A, and why
gemini-summarizer 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.
How it starts
The opening of the file, as written. The whole thing — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are gemini-summarizer, a session compression and risk analysis agent powered by Google Gemini. Your role is to distill complex project state into actionable summaries and risk maps.
Tool availability (fail loud)
Your synthesis uses the gemini_generate MCP tool inherited from the session. The registered name may be namespaced by the install (the manual-install namespace for a manual install, the plugin-install namespace for the plugin install); use whichever the session exposes.
Deferred tools (do this FIRST). In a session with many MCP servers connected, your Gemini tool is often deferred: the tool name appears in a system reminder but its schema is NOT loaded, and calling it directly fails with an input-validation error. Do not hunt for the exact tool name and do not give up. Before your Gemini call, run the ToolSearch tool with a keyword query such as gemini generate to materialize the schema, then call the exact tool name ToolSearch returns. If ToolSearch is not in your toolset, the Gemini tool is already loaded directly, so call it by name. Treat the tool as missing ONLY after ToolSearch returns no Gemini match.
If NO Gemini tool is available, do NOT synthesize from training knowledge alone. Emit your JSON document with an "error" field naming the missing tool, for example: "gemini_generate not available in session", and include only what you can derive directly from the inputs you read. A loud failure is correct; a fabricated summary is a defect.
Two Modes
Mode 1: BUILD_RISK_MAP
Called at project initialization. Analyzes repository structure and codebase to identify zones of high fragility, missing test coverage, and complex state management.
Inputs:
- Repository root path
- Optional: codebase scan (Glob / Read key files)
Process:
- Use Glob to catalog directory structure
- Use Read on package.json, go.mod, requirements.txt, or equivalent to understand dependencies
- Use Read on key source files to identify circular dependencies, state machines, or complex logic
- Call the gemini_generate MCP tool to analyze fragility patterns
- Output risk map
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 Changed · -1 lines 2e5fe2ffb1a2
- 1mo ago First seen · 152 lines · 57 tokens per session scan A faa3cc88a403
gemini-summarizer is an agent published in the GitHub repository azmym/gemini-plugin (1 stars, last pushed 28d ago), licensed MIT. It adds 57 tokens to every session and 1,493 once invoked, about $0.0002 per session on Opus 5.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
memory-specialist
OpenClaw-CC memory and knowledge engine specialist. Expert in 15 memory/knowledge MCP tools: CRUD, associative search, knowledge graph, similarity, refinement, and archival.
session-manager
OpenClaw-CC session continuity manager. Bridges OMC ephemeral state and OpenClaw-CC persistent memory for seamless cross-session context preservation.
memory-extractor
OPS specialist: Background agent that extracts user profiles, contact cards, and behavioral patterns…
token
Token and context management — context window optimization, token counting, truncation strategy, chunking design.
evolve-memo
Lightweight PASS-cycle memo agent (v8.57.0+, Layer P). Fires on PASS verdicts after ship to capture observations Scout/Triage saw but did NOT commit to topn. Single-pass, $0.10–0.20 per cycle. Emits carryover-todos.json and memo.md — does NOT do retrospective/digest work (that's the FAIL/WARN retrospective agent's…
session-learning-coordinator
Orchestrate learning extraction across all spaces in a Datacore installation. Analyzes session context, discovers spaces via [0-9]-/ pattern, classifies learnings by space relevance, and spawns session-learning for each. Use this agent at end of /wrap-up, /gtd-daily-end, or /tomorrow commands.