Plugins, skills, presets and marketplace

Extensions for each task

The plugin area shows installed plugins, their details and enabled state. Skills provide working instructions, hooks respond to events and MCP connections expose tools. Available capabilities depend on both the plugin and the agent using it.

The session view identifies plugins selected for the current session. After changing a plugin, you may need a new agent session to load its instructions. Having an extension does not automatically configure its external accounts.

Token usage and a shared plugin source

Expand a Claude plugin card to inspect the token figures reported by Claude Code. Always in context describes the continuously loaded portion; On use describes the portion loaded when a component is used. The table shows these figures for individual skills, commands or agents. Not measured means no figure is available. These are context-token figures, not a currency bill.

Your own installed plugins use one shared source for Claude and Codex. The workshop installs that source, links it to Claude and refreshes Codex's cache. Edit your authored plugin and start new sessions to load the updated instructions. If Codex is not installed yet, installation reports that and can synchronize it later.

Build and inspect your own plugins

The plugin builder opens a session where you describe the workflow you want. Alternatively, create an empty draft in the workshop. Open and review delivered drafts before installing them.

Use the workshop to edit existing content. The hook monitor and run log expose running, completed and problematic hooks. Inspect the individual run when something hangs before restarting the whole session.

Presets and custom commands

A preset packages a repeatable session start, such as a role, instructions, backend and supported model options. Create it in the preset library and use the editor to check which choices are fixed and which inherit settings.

Custom chat commands shorten repeated input. Shell and WSL startup profiles belong to their terminal setups. Presets and team profiles can follow your IXIOM account; local CLI installations and working files are not copied to another computer by that synchronization.

Reference files, knowledge and previews

Reference files such as documentation, configurations or examples are loaded in full when the session starts. Knowledge files are sources for the preset's identity: Merge as is or Summarize with AI first transfers their content into the identity field. Attached knowledge files do not reach the session while that field is empty.

Merge as is places file contents one after another without AI or an additional account. Summarize with AI uses the configured AI connection. Edit the resulting identity text directly in the editor. Open the generated agent-file preview before saving to check which instructions will actually be supplied.

Create preset with an agent starts the preset builder as a conversation. Describe the role, answer its questions and ask for revisions. Then review the model, permissions, references and identity in the preset editor.

Find and publish agents

The marketplace provides searchable, filterable agent listings, detail pages and a publishing dialog for your own agents. Check a listing's description, requirements and terms before using it.

A marketplace listing, an installed plugin and a saved preset serve different purposes. Choose an agent for a role, a plugin for additional capabilities and a preset for a repeatable starting point.