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.
npx agentmods add commands/cmdaltctr/claude-gemini-mcp-slim/analyzegit clone --depth 1 https://github.com/cmdaltctr/claude-gemini-mcp-slimWrote 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/commands/cmdaltctr/claude-gemini-mcp-slim/analyze)<a href="https://agentmods.dev/commands/cmdaltctr/claude-gemini-mcp-slim/analyze"><img src="https://agentmods.dev/badge/commands/cmdaltctr/claude-gemini-mcp-slim/analyze.svg" alt="Measured on agentmods" 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.00007 | $0.00133 |
| Opus 5 | $0.00003 | $0.00067 |
| Sonnet 5 | $0.00001 | $0.00027 |
| Haiku 4.5 | $0.00001 | $0.00013 |
Grade A, and why
analyze 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 6d 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
Code Analysis
Analyze code files for bugs, security issues, performance, and best practices.
Usage: /analyze [file_path] [analysis_type:optional]
Examples:
/analyze src/auth.py security/analyze components/UserForm.vue/analyze ./utils/database.js performance
Analyzing: $ARGUMENTS
!mcp__gemini-mcp__gemini_analyze_code code_content="@$1" analysis_type="$2"
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.
- 6d ago First seen · 20 lines · 7 tokens per session scan A abcf5beb3aab
analyze is a command published in the GitHub repository cmdaltctr/claude-gemini-mcp-slim (234 stars, last pushed 9mo ago), licensed MIT. It adds 7 tokens to every session and 133 once invoked, about $0.0000 per session on Opus 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-30.
Other commands, from other repositories
validate-gap
Analyze implementation gap between requirements and existing codebase.
bloat-scan
Scan for codebase bloat using 3-tier progressive analysis: dead code, duplication, God classes, and documentation waste.
unbloat
Remove dead code, duplicate files, and unused dependencies with user approval at each step. Backs up before deleting.
ox-doctor
Run diagnostic checks on SageOx configuration and integrations.
audit
Run a structured codebase audit. Maps the architecture, assesses health (compliance, tests, docs), performs deep analysis (security, performance, code quality), and synthesizes a prioritized roadmap. Outputs land under docs/audit/ in this project. Phases 0-3 with human checkpoints between each phase. Use /audit-quick…
wtfp:report-bug
Collect a reproducible bug report and publish it only after explicit user approval.