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/aaronsb/claude-code-config/geminigit clone --depth 1 https://github.com/aaronsb/claude-code-configWhat 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.00000 | $0.00675 |
| Opus 5 | $0.00000 | $0.00338 |
| Sonnet 5 | $0.00000 | $0.00135 |
| Haiku 4.5 | $0.00000 | $0.00068 |
Grade A, and why
gemini 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 2d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using Gemini CLI for Large Codebase Analysis
When analyzing large codebases or multiple files that might exceed context limits, use the Gemini CLI with its massive
context window. Use gemini -p to leverage Google Gemini's large context capacity.
Additionally, you can dispatch this as a subtask with your instructions based on these instructions to invoke Gemini, saving your own main context. This actually then allows you to invoke multiple Gemini threads.
File and Directory Inclusion Syntax
Use the @ syntax to include files and directories in your Gemini prompts. The paths should be relative to WHERE you run the
gemini command:
Examples:
Single file analysis: gemini -p "@src/main.py Explain this file's purpose and structure"
Multiple files: gemini -p "@package.json @src/index.js Analyze the dependencies used in the code"
Entire directory: gemini -p "@src/ Summarize the architecture of this codebase"
Multiple directories: gemini -p "@src/ @tests/ Analyze test coverage for the source code"
Current directory and subdirectories: gemini -p "@./ Give me an overview of this entire project"
Or use --all_files flag:
gemini --all_files -p "Analyze the project structure and dependencies"
Implementation Verification Examples
Check if a feature is implemented: gemini -p "@src/ @lib/ Has dark mode been implemented in this codebase? Show me the relevant files and functions"
Verify authentication implementation: gemini -p "@src/ @middleware/ Is JWT authentication implemented? List all auth-related endpoints and middleware"
Check for specific patterns: gemini -p "@src/ Are there any React hooks that handle WebSocket connections? List them with file paths"
Verify error handling: gemini -p "@src/ @api/ Is proper error handling implemented for all API endpoints? Show examples of try-catch blocks"
Check for rate limiting: gemini -p "@backend/ @middleware/ Is rate limiting implemented for the API? Show the implementation details"
Verify caching strategy: gemini -p "@src/ @lib/ @services/ Is Redis caching implemented? List all cache-related functions and their usage"
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.
- 2d ago First seen · 77 lines · 0 tokens per session scan A c273bbe32882
gemini is a command published in the GitHub repository aaronsb/claude-code-config (18 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 675 tokens. 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
ai-branch
AI 解读分支（L0 回退） — 演示无 keywordAliases 时由 AI Agent 解读自然语言触发分支.
kf-direct-support
TeamClaw 直接技能支持 — 直接调用 teamclaw-support 技能处理用户问题，跳过多阶段编排.
nyann:explain-state
Print a read-only summary of what nyann sees: stack, profile, branching, hooks, CLAUDE.md status, recent commits.
nyann:learn-profile
Inspect a reference repo and save its nyann-relevant setup (stack, hooks, branching, commit convention, extras) as a reusable profile.
nyann:migrate-profile
Switch this repository from one nyann profile to another. Computes a diff between source and target profiles, shows what will change (hooks, branching, extras, conventions), and applies via bootstrap.
nyann:optimize-claudemd
Analyze CLAUDE.md usage patterns and optimize content based on actual reference frequency. Removes unused sections, compresses low-density content, and adds frequently-used commands that are missing.