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/google-gemini/gemini-cli/introspectgit clone --depth 1 https://github.com/google-gemini/gemini-cliWhat 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.00148 |
| Opus 5 | $0.00000 | $0.00074 |
| Sonnet 5 | $0.00000 | $0.00030 |
| Haiku 4.5 | $0.00000 | $0.00015 |
Grade A, and why
introspect 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 today.
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
description = "Analyze the influence of system instructions on a specific action." prompt = """
Introspection Task
Take a step back and analyze your own system instructions and internal logic. The user is curious about the reasoning behind a specific action or decision you've made.
Specific point of interest: {{args}}
Please provide a detailed breakdown of:
- Which parts of your system instructions (global, workspace-specific, or provided via GEMINI.md) influenced this behavior?
- What was your internal thought process leading up to this action?
- Are there any ambiguities or conflicting instructions that played a role?
Your goal is to provide transparency into your underlying logic so the user can potentially improve the instructions in the future. """
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.
- today First seen · 17 lines · 0 tokens per session scan A 14fdde3dfb0a
introspect is a command published in the GitHub repository google-gemini/gemini-cli (106,761 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 148 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-09-02.
Other commands, from other repositories
package-assistant
Convert an OfficeCLI skill into a fully wired AionUi assistant preset, or update an existing one.
ask
Query multiple AI agents (Gemini, OpenAI, Grok, Perplexity, Kimi, and a local ollama model) for diverse perspectives on architecture decisions, technology choices, debugging dead-ends, and security tradeoffs. Use this whenever the user names the council directly, whatever the topic — ask the council, council review…
serve
Start the main 1MCP runtime with 1mcp serve and use it for CLI mode, direct HTTP MCP clients, and template-aware runtime behavior.
result
Fetch, list, or cancel background council jobs started with --async.
delegate
Delegate a well-scoped subtask to Antigravity (agy/Gemini) under cost discipline, then verify.
ask-all
Ask GPT, Gemini, Grok, and OpenRouter in parallel for independent second opinions.