Borrowing it
Nothing to install: this file belongs to vybestack/llxprt-code. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/vybestack/llxprt-code/main/.gemini/commands/introspect.tomlgit clone --depth 1 https://github.com/vybestack/llxprt-codeWrote 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/vybestack/llxprt-code/introspect)<a href="https://agentmods.dev/commands/vybestack/llxprt-code/introspect"><img src="https://agentmods.dev/badge/commands/vybestack/llxprt-code/introspect.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.00000 | $0.00150 |
| Opus 5 | $0.00000 | $0.00075 |
| 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 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.
This is a copy
94% identical to introspect — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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 LLXPRT.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.
- 2d ago First seen · 17 lines · 0 tokens per session scan A 0dd4bf92795e
introspect is a command published in the GitHub repository vybestack/llxprt-code (700 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 150 tokens. A static security scan graded it A with 0 findings. It is 94% identical to introspect, differing in 2 lines, and is treated as a copy.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.