---
title: "Plugin Architecture"
description: "OrchestKit ships as one unified plugin — everything loads on-demand with zero overhead."
canonical: "https://orchestkit.yonyon.ai/docs/foundations/choosing-a-plugin"
---

# Plugin Architecture

OrchestKit ships as one unified plugin — everything loads on-demand with zero overhead.

import { Count } from '@/components/count';

## One Plugin, Everything Included

OrchestKit ships as a single plugin: **ork**.

```bash
claude install orchestkit/ork
```

No choices, no configuration required. All <Count k="skills" /> skills, <Count k="agents" /> agents, and <Count k="hooks" /> hooks install together.

## What Loads When

Not everything runs at once. OrchestKit uses **on-demand loading** to stay fast:

| Component | When It Loads | Overhead |
|-----------|--------------|----------|
| **Hooks** | Session start — only event-matched hooks fire | ~800 tokens/turn max |
| **Agents** | When spawned by name or keyword match | Zero until invoked |
| **Skills** | Injected into agent context when relevant | Zero until matched |
| **Commands** | Available immediately via `/ork:skillname` | Listing only (~80 tokens/skill) |

## Why One Plugin

Early versions split functionality into multiple plugins (`orkl`, `ork-creative`). This caused:
- Version conflicts between plugins
- Duplicate hook registrations
- Confusing install instructions

Since v7.0, everything is consolidated into `ork`. Skills you don't use have zero token cost.

## Next Steps

- **[Installation](/docs/getting-started/installation)** — Full install guide with verification
- **[First 10 Minutes](/docs/getting-started/first-10-minutes)** — Guided first session