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 instructions/igniteui/igniteui-cli/claude-mdgit clone --depth 1 https://github.com/IgniteUI/igniteui-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.01036 | $0.01036 |
| Opus 5 | $0.00518 | $0.00518 |
| Sonnet 5 | $0.00207 | $0.00207 |
| Haiku 4.5 | $0.00104 | $0.00104 |
Grade A, and why
igniteui-cli CLAUDE.md 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.
How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Build, Test, Lint
yarn install # REQUIRED — must use yarn (not npm) for workspace resolution
npm run build # TypeScript compilation (tsc) + config schema generation
npm run test # lint + build + tests with coverage (via pretest hook)
npm run jasmine # tests only — no lint/build/coverage
npm run lint # ESLint (flat config in eslint.config.mjs)
To run a single test: edit spec/jasmine-runner.ts to filter spec_files, then npm run jasmine. Tests are Jasmine specs under spec/ (unit + acceptance) and within individual packages.
MCP Server (packages/igniteui-mcp/igniteui-doc-mcp)
Workspace package — part of yarn workspaces and lerna. Built automatically by npm run build via the build:mcp script. Has its own tsconfig.json (ES2022/ESM, separate from root CJS config).
npm run build:mcp # build MCP server (also runs as part of npm run build)
cd packages/igniteui-mcp/igniteui-doc-mcp
npm run build:db # build SQLite DB from compressed docs (manual step)
npm run pipeline:angular # incremental doc pipeline (also: react, blazor, webcomponents)
npm run pipeline:angular:full # full rebuild pipeline
npm run inspector # test with MCP Inspector
Architecture
Monorepo managed with lerna + yarn workspaces. Five packages:
| Package | npm | Path |
|---|---|---|
| CLI (entry point) | igniteui-cli |
packages/cli |
| Core (shared logic) | @igniteui/cli-core |
packages/core |
| Angular Templates | @igniteui/angular-templates |
packages/igx-templates |
| Angular Schematics | @igniteui/angular-schematics |
packages/ng-schematics |
| MCP Server | @igniteui/mcp-server |
packages/igniteui-mcp/igniteui-doc-mcp |
Core is the dependency root — changes to packages/core affect all other packages. Always rebuild the full monorepo after core 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.
- 2d ago First seen · 74 lines · 1,036 tokens per session scan A ce8ad7b83fff
igniteui-cli CLAUDE.md is an instructions file published in the GitHub repository IgniteUI/igniteui-cli (136 stars, last pushed 4d ago), licensed MIT. It adds 1,036 tokens to every session, about $0.0052 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-30.
Other instructions, from other repositories
spartan CLAUDE.md
Instructions for spartan-ng/spartan, covering working in this repo (notes for claude / ai agents), before pushing: run the ci checks locally and pull requests.
fundamental-ngx AGENTS.md
Instructions for SAP/fundamental-ngx, covering angular 22+ development guidelines, persona, quick reference, essential commands and build/lint/test specific library.
primitives CLAUDE.md
Instructions for radix-ng/primitives, covering radix ng primitives — claude guide, project knowledge, project overview, monorepo structure and naming conventions.
openbridge-webcomponents watch-radial-instruments.instructions.md
Instructions for Ocean-Industries-Concept-Lab/openbridge-webcomponents, covering watch & radial instruments, architecture overview, key principle: logic in watch.ts, instruments stay thin, shared sibling modules and layering & stacking pattern.
openbridge-webcomponents external-scale.instructions.md
Instructions for Ocean-Industries-Concept-Lab/openbridge-webcomponents, covering external scale & bar/gauge components, architecture overview, core renderer architecture, thin wrapper pattern and fixed-config gauge pattern.
openbridge-webcomponents line-area-charts.instructions.md
Instructions for Ocean-Industries-Concept-Lab/openbridge-webcomponents, covering line/area charts & gauge trend, architecture overview, key principle: logic in base class, subclasses stay thin, base class architecture and line graph (non-filled).