What Are the Dependencies of ag-kit? Complete Breakdown by Component

The ag-kit monorepo splits its dependencies across three isolated runtimes: the root package has no production dependencies, the CLI relies on five Node.js utilities (chalk, commander, fs-extra, giget, ora), and the documentation site depends on Next.js 16, React 19, and Tailwind 4.

The ag-kit repository is organized as a monorepo containing distinct CLI tooling and web documentation layers. Understanding the dependencies of ag-kit requires examining each component separately, as the project deliberately isolates runtime requirements between its command-line interface and Next.js-powered documentation site. This guide maps every production and development dependency declared in the project's package.json files.

Dependency Architecture Overview

The project is divided into three logical components, each with its own dependency footprint.

Root Package

The root package (package.json at the repository root) holds shared metadata and npm scripts. According to the source code at vudovn/ag-kit, this package does not ship any runtime code and consequently declares zero production dependencies. It functions purely as a workspace orchestrator.

CLI Dependencies

The command-line tool (cli/package.json) is built for Node.js ≥ 18 and declares five runtime dependencies responsible for terminal interaction and file system operations:

• chalk – Terminal string styling
• commander – Command-line interface framework
• fs-extra – Enhanced file system methods
• giget – Fast repository/template cloning
• ora – Elegant terminal loading spinners

No development dependencies are listed for the CLI component; testing relies on Node.js’s built-in test runner.

Web Documentation Dependencies

The documentation site (web/package.json) is a Next.js 16 application using React 19 and Tailwind 4. It maintains separate runtime and development dependency lists.

Runtime dependencies (lines 12‑26 of web/package.json):

• next (v16), react, react-dom – Core framework
• @base-ui/react – Unstyled UI primitives
• @mdx-js/react, @mdx-js/loader, @next/mdx, @types/mdx – MDX support
• lucide-react – Icon library
• class-variance-authority, tailwind-merge, tw-animate-css – Styling utilities
• next-themes – Theme management

Development-only dependencies (lines 27‑43 of web/package.json):

• typescript, @types/node, @types/react, @types/react-dom – Type definitions
• tailwindcss, @tailwindcss/postcss, babel-plugin-react-compiler – Build toolchain
• eslint, eslint-config-next – Linting
• gray-matter, remark-gfm – Content parsing
• rehype-autolink-headings, rehype-pretty-code, rehype-slug – Markdown transformation
• shiki – Syntax highlighting

Generated Agents

The .agents/ directory contains pure markdown-based toolkit templates. These templates do not declare their own dependencies; their runtime is provided by the Antigravity runtime layer, with validation handled by generated manifests. Consequently, there is no package.json within this directory.

Where Dependencies Are Declared

All versions are pinned in the specific manifest files:

1. CLI dependencies – Located in cli/package.json (lines 38‑44)
2. Web runtime dependencies – Located in web/package.json (lines 12‑26)
3. Web development dependencies – Located in web/package.json (lines 27‑43)

The root package.json only contains workspace configuration and npm scripts.

Installation and Usage Examples

Install the CLI globally to access its isolated dependency tree:

# Install the CLI globally (uses its own dependencies)

npm i -g @vudovn/ag-kit@2026.7.27

# Run the tool – it will internally use chalk, commander, fs‑extra, giget and ora

ag-kit init my‑agent

When developing the documentation site, Next.js loads the web-specific runtime dependencies:

// In the documentation site (web/), Next loads the runtime dependencies:
//   - next, react, react‑dom, @mdx-js/react, etc.
// Below is a minimal page that shows a component from the runtime deps:

import { Button } from '@base-ui/react';
import { Sun } from 'lucide-react';

export default function Home() {
  return (
    <main className="p-8">
      <Button>
        <Sun className="mr-2 h-4 w-4" /> Launch Agent
      </Button>
    </main>
  );
}

Summary

• The root package has no production dependencies; it serves only as a workspace coordinator.
• The CLI requires Node.js ≥ 18 and depends on five specific packages (chalk, commander, fs-extra, giget, ora) for terminal operations and file scaffolding.
• The Web component is a Next.js 16 application with separate runtime and development dependency sets, including React 19, Tailwind 4, and extensive MDX processing tools.
• Generated agents rely on the external Antigravity runtime and do not maintain their own dependency manifests.

Frequently Asked Questions

Does the root ag-kit package have any production dependencies?

No. The root package.json only contains repository metadata, workspace scripts, and shared configuration. It does not declare any production dependencies because it does not ship executable runtime code.

What Node.js version is required for the ag-kit CLI?

The CLI requires Node.js version 18 or higher. This requirement is specified in the CLI's package.json and ensures compatibility with the modern file system APIs used by fs-extra and the async patterns in giget.

Are the agent templates in .agents/ dependent on specific npm packages?

No. The agent templates are pure markdown-based toolkits. Their runtime is provided by the Antigravity runtime layer, which is validated through generated manifests. Consequently, the .agents/ directory does not contain a package.json or declare its own dependencies.

How do the documentation site dependencies differ from the CLI dependencies?

The CLI uses a minimal set of five focused utilities for terminal interaction and file system operations, while the documentation site maintains two distinct dependency lists: runtime dependencies for the Next.js/React application (including UI components and MDX processing) and development dependencies for TypeScript compilation, Tailwind processing, and content transformation pipelines.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}