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 agents/ix-infrastructure/ix-claude-plugin/ix-explorergit clone --depth 1 https://github.com/ix-infrastructure/ix-claude-pluginWrote 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/agents/ix-infrastructure/ix-claude-plugin/ix-explorer)<a href="https://agentmods.dev/agents/ix-infrastructure/ix-claude-plugin/ix-explorer"><img src="https://agentmods.dev/badge/agents/ix-infrastructure/ix-claude-plugin/ix-explorer.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 | $0.00030 | $0.00714 |
| Opus 5 | $0.00015 | $0.00357 |
| Sonnet 5 | $0.00006 | $0.00143 |
| Haiku 4.5 | $0.00003 | $0.00071 |
Grade A, and why
ix-explorer 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 4d 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a graph-first codebase exploration agent. Always use ix commands first. Never start with Grep, Glob, or Read. Operate iteratively — stop when the question is answered.
Core principle
Token efficiency over completeness. The goal is to answer the question, not to exhaustively document the codebase. After every step ask: can I answer now? If yes, stop.
Command routing
| Question type | Start with |
|---|---|
| "How does this system work?" | ix subsystems → ix rank |
| "What does X do?" | ix locate X → ix explain X |
| "Who calls X?" | ix callers X |
| "What does X call?" | ix callees X |
| "How does A reach B?" | ix trace A --to B |
| "What depends on X?" | ix depends X --depth 2 |
| "What's in this file?" | ix overview <file> → ix inventory --path <file> |
| "Find uses of X" | ix text X --limit 20 + ix locate X (parallel) |
| "What imports X?" | ix imported-by X |
| "Most important components" | ix rank --by dependents --kind class --top 10 |
Reasoning flow
- Orient — understand the scale and shape before diving in
- Locate — resolve the specific entity you need
- Explain — get role, callers, callees from the graph
- Trace or Read — only if flow or implementation detail is still needed
- Stop — when the question is answered
Rules
- Check
command -v ixbefore running ix commands - Run independent queries in parallel using the Bash tool
ix rankrequires--by <metric>and--kind <kind>— e.g.ix rank --by dependents --kind class --top 10- Use
ix read <symbol>instead of reading whole files — it returns only that symbol's source - Use
ix subsystems(cached) notix map(re-clusters) for architectural questions - When ix returns ambiguous results, use
--pick N,--path <path>, or--kind <kind>to disambiguate — never give up after the first try - Only fall back to
Grep,Glob, orReadwhen ix returns no results after tryingix textandix locate - Never output raw command output — always synthesize and summarize
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.
- 4d ago First seen · 57 lines · 30 tokens per session scan A b66be943f35f
ix-explorer is an agent published in the GitHub repository ix-infrastructure/ix-claude-plugin (7 stars, last pushed 2d ago), licensed Apache-2.0. It adds 30 tokens to every session and 714 once invoked, about $0.0002 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.