Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/ix-infrastructure/ix-claude-pluginnpx agentmods add skills/ix-infrastructure/ix-claude-plugin/ix-investigateWrote 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/skills/ix-infrastructure/ix-claude-plugin/ix-investigate)<a href="https://agentmods.dev/skills/ix-infrastructure/ix-claude-plugin/ix-investigate"><img src="https://agentmods.dev/badge/skills/ix-infrastructure/ix-claude-plugin/ix-investigate/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/ix-infrastructure/ix-claude-plugin/ix-investigate"><img src="https://agentmods.dev/badge/skills/ix-infrastructure/ix-claude-plugin/ix-investigate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00029 | $0.01185 |
| Opus 5 | $0.00015 | $0.00593 |
| Sonnet 5 | $0.00006 | $0.00237 |
| Haiku 4.5 | $0.00003 | $0.00119 |
Grade A, and why
ix-investigate 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 10d 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Check command -v ix first. If unavailable, use Grep + Read as fallback.
Argument parsing
Strip --save and any following path token from $ARGUMENTS before resolving the target.
- If
--save <path>is present, setSAVE_PATHto that path. - If
--saveis present without a path, auto-generateix-investigate-<target-slug>.mdin cwd (target slug = the target with spaces and slashes replaced by-). - If
--saveis absent,SAVE_PATHis empty — do not write a file.
Pro check (optional)
Run once at the start:
ix briefing --format json 2>&1
If it returns JSON with a revision field, Pro is available. Extract recentDecisions and openBugs for use in Pro steps below. If it errors, skip all [Pro] labeled steps.
Goal
Answer: what is this, how does it connect, and what's the execution path? Stop as soon as those three questions can be answered accurately.
Phase 1 — Locate (always)
ix locate $ARGUMENTS --format llm
If multiple matches: use --kind, --path, or --pick N to resolve. Do not proceed until the entity is unambiguous.
If ix locate returns nothing: try ix text $ARGUMENTS --limit 10 --format llm.
Phase 2 — Explain (always)
ix explain <resolved-symbol> --format llm
Extract: role, importance, caller count, callee count, confidence score.
If the resolved entity is a class or module, also run:
ix overview <resolved-symbol> --format llm
This reveals internal structure (members, sub-components) without reading source.
Orphan check: If fan_in = 0 AND fan_out = 0 in the ix explain output:
- Report: "Symbol is a graph orphan — no detected dependencies. Either the graph needs a refresh (
ix map) or the file has no parseable import/call relationships." - Suggest
ix map <file>as first step. - Stop here — skip Phases 3–5 unless the user specifically asks for source-level inspection.
Evaluate: Is the explanation sufficient to answer the question?
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.
- 10d ago First seen · 136 lines · 29 tokens per session scan A f71c73537cec
ix-investigate is a skill published in the GitHub repository ix-infrastructure/ix-claude-plugin (7 stars, last pushed today), licensed Apache-2.0. It adds 29 tokens to every session and 1,185 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-31.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.