ix-docs

ix-docs is a skill for Claude Code, Codex from ix-infrastructure/ix-claude-plugin. It costs 37 tokens per session (4,465 once invoked), scanned A, original, Apache-2.0.

A documentation skill that creates an onboarding explanation of a code repository or subsystem, followed by concise reference notes for important parts. A repository is the project's source files and related history.

In plain words
What is it for?
Use it to document architecture, flows, usage, risks, important file locations, and selected modules; use full mode for deeper coverage.
Why use it?
It helps a new engineer understand how the system works without reading a low-value dump of every file, class, or method.

Skill for Claude CodeCodex

Part of the ix-memory plugin — 7 skills, 5 agents, 4 hooks shipped together

Install

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.

agentmods
npx agentmods add skills/ix-infrastructure/ix-claude-plugin/ix-docs
Any agent
npx skills add ix-infrastructure/ix-claude-plugin --skill ix-docs
Clone the repo
git clone --depth 1 https://github.com/ix-infrastructure/ix-claude-plugin

Made for: Claude Code, Codex.

Or install ix-memory, the plugin that ships this one along with the rest of its 7 skills, 5 agents, 4 hooks.

Wrote 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.

agentmods badge for ix-docs

README.md
[![agentmods](https://agentmods.dev/badge/skills/ix-infrastructure/ix-claude-plugin/ix-docs.svg)](https://agentmods.dev/skills/ix-infrastructure/ix-claude-plugin/ix-docs)
Your own site
<a href="https://agentmods.dev/skills/ix-infrastructure/ix-claude-plugin/ix-docs"><img src="https://agentmods.dev/badge/skills/ix-infrastructure/ix-claude-plugin/ix-docs.svg" alt="Measured on agentmods" height="20"></a>
Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,465 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00037 $0.04465
Opus 5 $0.00018 $0.02233
Sonnet 5 $0.00007 $0.00893
Haiku 4.5 $0.00004 $0.00447

Measured 5d ago against content hash 7e46fbfb46b4, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ix-docs 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 5d 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.

skills/ix-docs/SKILL.md · 556 lines

How it starts

The opening of the file, as written. The whole thing — 556 lines — stays where its author put it; the contents beside it link to each section on GitHub.

ix-claude-plugin shared model

Check command -v ix first. If unavailable, stop and say so.

Goal

Produce documentation that helps a new engineer understand the system quickly and gives an LLM strong architectural context without drowning it in low-value detail.

Write like real engineering documentation for a framework or subsystem:

  • teach the system
  • explain how it works
  • show where the important parts live
  • surface risks and fragile boundaries
  • point the reader to the next files or symbols to inspect

Never write a raw report dump.


Core model

Every ix-docs run produces two layers:

  1. Narrative layer (always first)

    • human-readable explanation
    • onboarding-focused
    • architecture, flow, usage, risks, navigation guidance
  2. Reference layer (always present, but selective)

    • compressed summaries of important modules, classes, and services
    • short, structured, high-signal entries
    • no code dumping

Mode behavior

  • ix-docs <target>: narrative-heavy by default, with a minimal selective reference appendix
  • ix-docs <target> --full: deeper coverage for important components, still importance-weighted

Style behavior

  • --style narrative (default): prose-first narrative sections; reference layer stays compact
  • --style reference: tighter, docs-site style structure; narrative stays brief but is not removed
  • --style hybrid: full narrative plus fuller selective reference; best match for --full

Flags

Fragment Variable Default
first non-flag token TARGET required
--full FULL=true false
`--style narrative reference hybrid`
--split SPLIT=true false
--single-doc SINGLE=true false
--out <path> OUT_PATH auto-detect
--save [path] alias for --out when --out is absent; if both are given, --out wins

Parsing Scan $ARGUMENTS left to right:

  • The first token that does not begin with -- is TARGET
  • --style and --out consume the next token as their value (also accept --style=value form)
  • All other flags are boolean toggles
  • If TARGET is missing, stop and ask the user to supply a target before continuing

Read the full file on GitHub · 556 lines

Changes

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.

  1. 5d ago First seen · 556 lines · 37 tokens per session scan A 7e46fbfb46b4

Subscribe to this mod's changes

ix-docs is a skill published in the GitHub repository ix-infrastructure/ix-claude-plugin (7 stars, last pushed 3d ago), licensed Apache-2.0. It adds 37 tokens to every session and 4,465 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens