context-course/pr_7/en/unit3/introduction.md

# Unit 3: Plugins

## What Are Plugins?

Plugins are reusable extensions for code agents. The exact shape depends on the platform: **Claude Code** and **Codex** use installable plugin bundles with manifests plus optional skills, MCP servers, and app integrations, while **OpenCode** uses JavaScript/TypeScript plugin modules loaded from local files or npm packages.

Plugins are pre-built context packs: curated, tested, and shareable bundles of knowledge and tools that save setup time and keep teams consistent.

## The Evolution of Context

The journey to plugins reflects how AI agents have matured:

1. **Prompts** — Raw instructions. Fragile, hard to reuse, inconsistent across team members.
2. **Skills** — Packaged prompts + tools. More organized, but no dependency management.
3. **MCP Servers** — Standardized tool interfaces. Composable, but steep learning curve.
4. **Plugins** — Reusable extensions. In Claude Code and Codex, that usually means a manifest plus bundled components. In OpenCode, it means a code module that hooks into the agent and can add behavior or tools.

## Why Plugins Matter

For a solo developer, a plugin skips setup: install a Python-linting plugin or an API-docs plugin and you inherit someone else's curation. For a team, plugins are the unit of consistency — everyone gets the same tools and instructions. For a community, they're a shareable artifact you can publish to a marketplace.

## Key Terminology

A **skill** is a reusable prompt plus metadata. An **MCP server** is a standardized tool provider for file I/O, API calls, or database queries. An **integration** connects to an external service like GitHub, Slack, or Google Drive. A **manifest** is the metadata file used by manifest-first plugin systems like Claude Code and Codex. A **marketplace** is a catalog where plugins are published and discovered.

First up, we are going to take an in-depth look at the anatomy of plugins.