What is idux-mcp AGENTS.md?

A set of instructions for coding agents working on idux-mcp, an MCP server for the iDux UI component library. It covers the project structure, development commands, testing, and debugging.

Use it when developing the TypeScript server, downloading or searching cached iDux components and documentation, running Vitest tests, or debugging MCP behavior.

It gives an agent the repository-specific information needed to build, test, inspect, and troubleshoot the server correctly.

How hangboss1761/idux-mcp configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to hangboss1761/idux-mcp. 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/hangboss1761/idux-mcp/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/hangboss1761/idux-mcp

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/hangboss1761/idux-mcp/agents-md/github.svg)](https://agentmods.dev/instructions/hangboss1761/idux-mcp/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/hangboss1761/idux-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/hangboss1761/idux-mcp/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/hangboss1761/idux-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/hangboss1761/idux-mcp/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 931 This file is loaded in full into every session.

When invoked 931 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.

Model	Per session	Once invoked
Fable 5.1	$0.00931	$0.00931
Opus 5	$0.00465	$0.00465
Sonnet 5	$0.00186	$0.00186
Haiku 4.5	$0.00093	$0.00093

Measured 9d ago against content hash 848ddc94b733, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

idux-mcp 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 · 100 lines

How it starts

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

AGENTS.md

This file provides guidance to Coding Agents when working with code in this repository.

Project Overview

This is an MCP (Model Context Protocol) server for iDux UI component library. It provides intelligent access to iDux components, documentation, and examples for developers and AI assistants. The server downloads and caches iDux source code from GitHub, then provides tools to search and retrieve component information.

Development Commands

Building and Development

pnpm build - Build the project using tsup (creates dist/ with ESM and CJS formats)
pnpm watch - Watch mode for continuous development and rebuilding
pnpm clean - Clean dist and node_modules directories

Testing

pnpm test - Run all tests with Vitest
pnpm test:watch - Run tests in watch mode
pnpm test:coverage - Run tests with coverage report

Debugging

pnpm inspector - Use MCP Inspector tool for debugging the server
LOG_LEVEL=debug pnpm build && node dist/index.js - Run with debug logging

Architecture

Core Components

IduxServer (src/server.ts): Main MCP server implementation that handles:
- Tool registration and routing
- Error handling with decorators
- Component search and retrieval logic
- Cache management coordination
CacheManager (src/cache.ts): Manages component information caching:
- Downloads and extracts iDux source code from GitHub
- Processes component docs and demos into structured format
- Maintains cache in ~/.idux-mcp/cache/
- Generates info.json with component metadata
SourceManager (src/repository.ts): Handles source code acquisition:
- Downloads zip files from GitHub
- Extracts to temporary directories
- Cleans up temporary files
Logger (src/logger.ts): Singleton logging system using Winston:
- Logs to ~/.idux-mcp/logs/
- Configurable log levels via LOG_LEVEL environment variable

MCP Tools Available

list_idux_components - Get all available components
get_component_details - Get detailed component information including API docs
get_component_examples - Get usage examples for components
search_components - Search components by keywords
update_components_cache - Manually update component cache

Read the full file on GitHub · 100 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.

9d ago First seen · 100 lines · 931 tokens per session scan A 848ddc94b733

Subscribe to this mod's changes

idux-mcp AGENTS.md is an instructions file published in the GitHub repository hangboss1761/idux-mcp (0 stars, last pushed 9mo ago), licensed MIT. It adds 931 tokens to every session, about $0.0047 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.

Debugging

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,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,153 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 · 6,785 tokens

idux-mcp: Instructions file for Codex

Borrowing it

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

AGENTS.md

Project Overview

Development Commands

Building and Development

Testing

Debugging

Architecture

Core Components

MCP Tools Available

What this file has done since we first saw it

Other instructions, from other repositories

next.js AGENTS.md

codex AGENTS.md

vscode buildNext.instructions.md

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

langchain AGENTS.md

deepseek-harness AGENTS.md