Use Maxtkn
Your own agents and teams, rules, skills, slash commands, MCP servers and hooks. Install bundles, import from other tools, and give the team your documents.
Last updated
Everything that shapes how the team works is in one place: the Customize screen on the left rail. It lists, by kind, what is active: Agents, Teams, Rules, Skills, Commands, MCP servers and Hooks. Each row says what it does and where it came from (built in, this project, yours, or imported from Cursor, Claude or VS Code), and has an on/off switch where the kind has one. The info button explains what overrides what.
| Kind | What it is | Where it lives |
|---|---|---|
| Instructions | Plain-language guidance for every run. Maxtkn reads AGENTS.md as it is. | AGENTS.md in the project |
| Rules | Guidance that always applies, applies to certain files, or applies only when you @name it. .cursor rules are read as they are. | .maxtkn/rules |
| Skills | SKILL.md folders made for other tools work unchanged. Switch any skill off per project. | .agents/skills/<name>/SKILL.md |
| Commands | Your own workflows as /commands. Files are Markdown with an optional description; $ARGUMENTS is what you type after the name. | .maxtkn/commands/*.md, or Settings → Commands for all projects. .claude/commands and .cursor/commands are read too. |
| MCP servers | Extra tools from servers that follow the Model Context Protocol. | .maxtkn/mcp.json |
| Hooks | Programs that run at set moments, for example before a tool call. | .maxtkn/hooks.json |
New in the Customize screen creates a starter file in the right place and opens it for editing. Anything in a project that could run a program (hooks, MCP servers, skill scripts) runs only after you trust the project (see below).
Rules, skills, commands and MCP servers can belong to one project or to all your projects. The two places never mix: Settings → Extensions holds only what you put there yourself, and every project gets it from its next run. Customize is about the project you have open: its own files, plus your global items so you can see everything in force.
A folder that ships its own hooks, MCP servers or skill scripts asks you once and lists exactly what would run. Until you agree they do not run. In the command line the same things are listed as skipped unless you pass --trust.
A bundle is one file or folder, maxtkn-plugin.json, that adds agents, teams, rules, skills, commands, MCP servers and hooks in one step. Install from a folder, a git address, a file or pasted text. Before anything is installed you see a preview of everything it adds. Anything that runs a program or reaches a network is off until you tick it. Credentials are installed empty. Uninstalling removes exactly what the bundle added, and you can update it in place.
Customize → Import from other tools reads a project’s Cursor rules and .cursorrules, Copilot instructions, Claude skills (as text only, never scripts) and commands, and MCP servers and hooks. You see the exact text first, nothing is overwritten, programs are left unticked and credentials are written empty. Only the project’s own folders are read, not your home folder.
Settings → Workspace → Project knowledge lets the team look things up in your project’s documents and shared notes instead of reading whole files. It searches documents, never code. A card in the thread shows what was looked up. The built-in search matches words and does not understand synonyms, so use the words your documents use.
Settings → General → Appearance has a light theme, a dark theme, high contrast and reduced motion, and each can follow your device’s setting.
Something missing or wrong? Maxtkn is early-access software and these pages change with it. The changelog lists what changed in each build.