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/codebasegit clone --depth 1 https://github.com/cmdaltctr/claude-gemini-mcp-slimWhat 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 | $0.00011 | $0.00130 |
| Opus 5 | $0.00005 | $0.00065 |
| Sonnet 5 | $0.00002 | $0.00026 |
| Haiku 4.5 | $0.00001 | $0.00013 |
Grade A, and why
codebase 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
Codebase Analysis
Analyze entire directories and codebases with Gemini's large context window.
Usage: /codebase [directory_path] [scope:optional]
Examples:
/codebase ./src/codebase ./components security/codebase . all
Analyzing codebase: $ARGUMENTS
!mcp__gemini-mcp__gemini_codebase_analysis directory_path="$1" analysis_scope="$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.
- yesterday First seen · 20 lines · 11 tokens per session scan A 6aa07a91a23a
codebase is a command published in the GitHub repository cmdaltctr/claude-gemini-mcp-slim (234 stars, last pushed 9mo ago), licensed MIT. It adds 11 tokens to every session and 130 once invoked, about $0.0001 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
openspec-proposal
Scaffold a new OpenSpec change and validate strictly.
openspec-archive
Archive a deployed OpenSpec change and update specs.
openspec-apply
Implement an approved OpenSpec change and keep tasks in sync.
spec-design
Create comprehensive technical design for a specification.
create-hook
Create hooks with brainstorming and security-first design.
ox-session-pause
belongs in the ox CLI JSON output (guidance field), not here. Skills are agent-specific wrappers; ox serves all agents (Codex, etc.). --> Suspend the current session recording. Local cache continues to receive entries, but the upload at stop time will exclude the suspended range.