igniteui-cli: Instructions file for Codex

AGENTS.md

igniteui-cli AGENTS.md is an instructions file for Codex, OpenCode from IgniteUI/igniteui-cli. It costs 2,082 tokens per session, scanned A, original, MIT.

Repository instructions for AI coding agents working on Ignite UI CLI. They document how to install dependencies, build, lint, run tests, use the model context protocol server, and check generated projects.

In plain words
What is it for?
Use them when changing the CLI, templates, tests, or the model context protocol server. They help choose the right build, test, lint, and smoke-test commands.
Why use it?
They give an agent the project's required commands and boundaries, reducing mistakes such as using the wrong package manager or relying on tests that do not compile a generated project.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions subagents; mentions AGENTS.md.

This is IgniteUI/igniteui-cli's own configuration. It tells Codex and OpenCode how to work on igniteui-cli itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything igniteui-cli configures →

Reuse

Borrowing it

Nothing to install: this file belongs to IgniteUI/igniteui-cli. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/IgniteUI/igniteui-cli/master/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/IgniteUI/igniteui-cli

Made for: Codex, OpenCode.

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 igniteui-cli AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/igniteui/igniteui-cli/agents-md/github.svg)](https://agentmods.dev/instructions/igniteui/igniteui-cli/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/igniteui/igniteui-cli/agents-md"><img src="https://agentmods.dev/badge/instructions/igniteui/igniteui-cli/agents-md/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.

agentmods 80×15 button for igniteui-cli AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/igniteui/igniteui-cli/agents-md"><img src="https://agentmods.dev/badge/instructions/igniteui/igniteui-cli/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 2,082 This file is loaded in full into every session.
When invoked 2,082 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.02082 $0.02082
Opus 5.5 $0.00833 $0.00833
Sonnet 5.5 $0.00416 $0.00416
Haiku 4.5 $0.00208 $0.00208

Measured 9d ago against content hash 454e8e2f1823, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

igniteui-cli AGENTS.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 9d 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.

AGENTS.md · 97 lines

How it starts

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

AGENTS.md

Guidance for AI coding agents working in this repository.

Build, Test, Lint

yarn install                    # REQUIRED — must use yarn (not npm) for workspace resolution
npm run build                   # tsc + config schema generation + MCP server build
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)
scripts/smoke-test.sh           # scaffold + add every template + install + build

Tests are Jasmine specs under spec/ (unit + acceptance) and within individual packages.

scripts/smoke-test.sh is the only check that a generated project actually installs and builds — the Jasmine specs stub PackageManager.installPackages. Run it after touching anything under packages/cli/templates/ or packages/igx-templates/. Running one spec file, the specs that guard templates, running the smoke test, reading its results and editing the script: igniteui-cli-smoke-test skill.

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

Adding or changing an MCP tool (schema, handler, description, tests, every doc that lists the tool): igniteui-cli-mcp-tool skill.

Architecture

Monorepo managed with lerna + yarn workspaces. Five packages:

Read the full file on GitHub · 97 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. 9d ago First seen · 97 lines · 2,082 tokens per session scan A 454e8e2f1823

Subscribe to this mod's changes

igniteui-cli AGENTS.md is an instructions file published in the GitHub repository IgniteUI/igniteui-cli (137 stars, last pushed today), licensed MIT. It adds 2,082 tokens to every session, about $0.0083 per session on Opus 5.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-10-21.

Related

Other instructions, from other repositories

create-trimble-app components.instructions.md

Instructions for julianoczkowski/create-trimble-app, covering modus wrapper component patterns, event handling pattern, state management, props pattern and modal implementation.

julianoczkowski/create-trimble-app · 442 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,715 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,461 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,750 tokens